Bugzilla – Bug 540525
genprof / logprof crash: LibAppArmor.so: undefined symbol: parse_record
Last modified: 2009-10-13 19:32:18 UTC
I get the following error when running - genprof (appears after (S)canning the log) - logprof (directly after startup) /usr/bin/perl: symbol lookup error: /usr/lib/perl5/vendor_perl/5.10.0/x86_64-linux-thread-multi/ /auto/LibAppArmor/LibAppArmor.so: undefined symbol: parse_record This means it's impossible to create or modify profiles! (perl-libapparmor-2.3-54.14.x86_64, apparmor-utils-2.3.1-11.7.noarch) (this bug is the command-line part of bug 535107)
sounds okaish to fix this with online updates.
Coolo, are you joking? I'll probably give a talk about AppArmor on the Open Source Expo Karlsruhe (15th and 16th november 2009 - aka some days after 11.2 release). It would be a pity if I would have to use a 11.1 installation to demo AppArmor. And it would be even worse if I have to finish my talk with "Oh, by the way: If you want to create your own profiles, you'll have to use 11.1 because the AppArmor tools are totally broken in 11.2!" -> Please reconsider the priority / timeframe of fixing this bug!
that you're interested in apparmor is fine, but doesn't change the fact that creating profiles is far from mainstream. Oh, and I'm sure Jeff accepts patches. As long I prefer Jeff working on kernel fixes that affect many - e.g. like 533556 where online updates are no option.
Far from mainstream? - not at all!! As long as we do not have working default profiles for programs like Cups, Thunderbird, Kopete or even Firefox, Apparmor will at all be of little help. Please do rethink the priority.
If we have some issues of direly high priority then this is no reason to fully drop the priority of other quite important issues!
Can you try the packages from Factory? I could reproduce this and then I rebuilt the packages -without modifying anything- and it worked afterwards.
I had exactly the same problem yesterday when trying to create a profile for skype and since then there are no new updates available. $ rpm -qa | grep armor apparmor-parser-2.3.1-10.28.x86_64 pam_apparmor-2.3-52.7.x86_64 apparmor-utils-2.3.1-11.7.noarch apparmor-docs-2.3.1-10.31.noarch libapparmor1-2.3-54.14.x86_64 perl-libapparmor-2.3-54.14.x86_64 yast2-apparmor-2.18.3-1.4.noarch apparmor-profiles-2.3-49.1.noarch So, perhaps a rebuild _might_ fix it but the current published ones are still broken.
Here's the strange part. I installed libapparmor1-2.3-54.17 from Factory and it failed. I downloaded the srpm for libapparmor1-2.3-54.17 and built it locally and it worked fine.
then add SUSE_ASNEEDED=0 to the spec file.
So what does that do and why does it work locally but not in OBS or mbuild?
Coolo replied out-of-band that it's only set in the build systems by default. I've set that and built in mbuild and verified that it works. Committed to the build service and submitted SR 22342. Closing as FIXED.
BTW, in the interim, I've placed the fixed packages here: http://ftp.suse.com/pub/people/jeffm/suse/testpkgs/540525 It may take several moments to sync out.
Thanks for the packages on ftp.suse.com - they fix the crash :-) Unfortunately this doesn't help much - logprof doesn't crash, but it doesn't do anything because of changed audit.log format. :-( I just opened bug 546618 for that...