torbrowser-apparmor-profile: Starting torbrowser-launcher shows segfault in dmesg

[ghost]

I am using torbrowser-launcher on openSUSE Leap 42.3 and I have been advised by openSUSE to report this upstream here.

On each start of Tor browser when apparmor is running in journalctl I see:

Apr 30 19:53:27 pc kernel: firefox[9287]: segfault at 0 ip 00007fa91b876cff sp 00007ffd5cd045c8 error 6 in libxul.so[7fa9196d1000+4413000]
Apr 30 19:53:28 pc dbus[1411]: [system] Failed to activate service 'org.bluez': timed out
Apr 30 19:53:31 pc systemd-coredump[9288]: Process 9287 (firefox) of user 1000 dumped core.

When I stop apparmor.service and watch journalctl -f there are no segfaults.

[intrigeri]

On each start of Tor browser when apparmor is running in journalctl I see:

Apr 30 19:53:27 pc kernel: firefox[9287]: segfault at 0 ip 00007fa91b876cff sp 00007ffd5cd045c8 error 6 in libxul.so[7fa9196d1000+4413000]
Apr 30 19:53:28 pc dbus[1411]: [system] Failed to activate service 'org.bluez': timed out
Apr 30 19:53:31 pc systemd-coredump[9288]: Process 9287 (firefox) of user 1000 dumped core.

When I stop apparmor.service and watch journalctl -f there are no segfaults.

Wow, interesting. I've never seen that on Debian. What kernel are you running?

Is there any AppArmor denial logs in the Journal?

[ghost]

What kernel are you running?

[~]: uname -a
Linux i7 4.4.126-48-default #1 SMP Sat Apr 7 05:22:50 UTC 2018 (f24992c) x86_64 x86_64 x86_64 GNU/Linux

Is there any AppArmor denial logs in the Journal?

No. When I start Tor browser journalctl -f shows only the lines which I pasted in the first post.

[intrigeri]

Thank you. Wow, 4.4 is old. Not sure what's the status of AppArmor patches in there. I'm afraid I can't support anything older than 4.9 :/

[intrigeri]

Tor Browser 8.0a10 fixes a segfault on old distros. It would be nice to test it with torbrowser-launcher's develop branch.