On 1/28/21 2:54 PM, Jonas Große Sundrup wrote:
> On 2020-09-05, John Johansen wrote:
>> This would point to a kernel change. Do you know how to bisect? Or are
>> you willing to test debug kernels built for you based on a bisect.
>
> Yes, unfortunately due to time constraints I didn't get around to
On 2020-09-05, John Johansen wrote:
> This would point to a kernel change. Do you know how to bisect? Or are
> you willing to test debug kernels built for you based on a bisect.
Yes, unfortunately due to time constraints I didn't get around to
bisecting the problem just yet. I, however, also notic
On 9/5/20 2:23 AM, John Johansen wrote:
> On 8/28/20 12:24 PM, Jonas Große Sundrup wrote:
>> Hi,
>>
>> I apparently just ran into a kernel regression with AppArmor and I'm
>> looking for the correct bugtracker now.
>>
>> The situation at hand is roughly the following:
>>
>> /usr/bin/element-desktop
On 8/28/20 12:24 PM, Jonas Große Sundrup wrote:
> Hi,
>
> I apparently just ran into a kernel regression with AppArmor and I'm
> looking for the correct bugtracker now.
>
> The situation at hand is roughly the following:
>
> /usr/bin/element-desktop
> is a bash-script, therefore spawns a bash
On 8/30/20 8:50 AM, Jonas Große Sundrup wrote:
> Hi,
>
>
> On 2020-08-30, Christian Boltz wrote:
>> - did you reload the profile after changing it?
>
> Yes, via aa-teardown && systemctl restart apparmor.service and
> restarting element-{desktop,launcher} afterwards for the profiles to
> take eff
Hi,
On 2020-08-30, Christian Boltz wrote:
> - did you reload the profile after changing it?
Yes, via aa-teardown && systemctl restart apparmor.service and
restarting element-{desktop,launcher} afterwards for the profiles to
take effect. I have made sure that no processes of
element-{desktop,laun
Hello,
Am Freitag, 28. August 2020, 21:40:36 CEST schrieb Jonas Große Sundrup:
> Ok, things get funky, I tried some arbitraty things and found...
> interesting behavior:
[...]
> Does anyone have an idea what could be going on here?
No exact idea, but some guesses: [1]
- did you reload the profile
Ok, things get funky, I tried some arbitraty things and found...
interesting behavior:
Namely, I have copied that bashscript /usr/bin/element-desktop to
/usr/local/bin/elementlauncher and copied the profile for
element-desktop to a second file, and only adjusted the path.
So /usr/bin/element-desk
Hi,
I apparently just ran into a kernel regression with AppArmor and I'm
looking for the correct bugtracker now.
The situation at hand is roughly the following:
/usr/bin/element-desktop
is a bash-script, therefore spawns a bash
spawns "electron /usr/lib/element/element.asar"
I have a prof
