New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Apparmor Seg Fault #28127
Comments
Does it happen with It's been a while since I touched my apparmor stuff (I just leave it on), but I can test locally later. @paper42 or @CameronNemo have you experienced anything similar? |
There is a deleted post on reddit about this issue, archive.org doesn't have it. I can not reproduce it on my musl machine (tested both complain or enforce mode). |
Yes it still happens with complain |
And i know about the deleted post. I said im not the first one while i was asking for help on matrix because i saw it. |
sorry that was an accident |
why is your kernel so old? 5.3??? |
I wanted something more LTS but both 4.14 and 4.19 broke some things so i chose 5.3....but i just realised after double checking 5.4 is the lts one and im an actual moron. |
Im now running 5.4 |
Ok, I can't reproduce this here. Have you tried running What I would ask is that you install the debug packages necessary for apparmor ( |
i checked the packages with xbps-pkgdb and its all dandy |
Is that all that was printed? Actually, please use the following commands inside GDB: |
|
Is |
theres no such package in the repository. The command u gave me installed gdb |
Ok, sorry; you needed a few more things for that command to work the way I intended. What you should do, then, is run:
|
|
This seems to be missing some information again :/ |
i did what u told me man :d |
Run the steps from here : #28127 (comment) |
thats what i did tho |
I managed to reproduce this on 5.4 kernel on musl:
|
Ah, so kernel version matters. Thanks! |
are yall just gonna force me to use the latest kernel lol |
Is |
That's just GDB saying it can't find the source for musl's vfprintf. So yes, it is the missing file. The actual error is a segfault. @anon-lestat no one was telling you to do that; we were just gathering information on what environment is being used that breaks apparmor. Void does still support multiple LTS kernels. |
ah cool |
Ok this is stupid. In all cases |
* add missing dependency python3-notify2 for aa-notify * do not rewrite logfiles option in logprof.conf aggressively * remove an old patch * fix segfault on musl closes void-linux#28127
* add missing python3 dependencies for aa-notify * do not rewrite logfiles option in logprof.conf aggressively * remove an old patch * fix segfault on musl (was also an issue on glibc, just empty output instead of segfault) * depend on explicit libapparmor version Closes void-linux/void-packages#28127 void-linux/void-packages@5251fe6
Void 5.3.18_1 x86_64-musl GenuineIntel uptodate rDDFFF
apparmor-3.0.1_1
Expected behavior
aa-status:
Apparmor module is loaded
Lists all the profiles
Actual behavior
aa-status:
Apparmor module is loaded
Segmentation fault
Steps to reproduce the behavior
The text was updated successfully, but these errors were encountered: