Bugzilla – Bug 399676
Empty list of profiles
Last modified: 2008-06-17 16:05:23 UTC
Created attachment 221801 [details] y2logs There are no profiles shown in the list, even the default profiles are not shown. Attached y2logs.
what module are you talking about?
Both, editing and deleting apparmor profiles
*** Bug 399678 has been marked as a duplicate of this bug. ***
Please try to reproduce, this time with Y2DEBUG=1 as there's desperately few information in y2log (http://en.opensuse.org/Bugs/YaST#The_y2logs_don.27t_seem_to_show_my_problem._Can_that_logging_be_made_any_more_verbose.3F)
I maintain yast2-core, so as a side quest I am interested why we do not get more details than "Y2ProgramComponent.cc(receiveFromExternal):358 External program returned invalid data." in the log. It turns out that it happens only when the program does not produce any output. Otherwise that error would be preceded by a parser error. It turns out that when I run the modules outside the control center, I get quite a few interesting errors from Perl: (I haven't touched AA configuration before) # yast2 SD_DeleteProfile # or SD_EditProfile, same errors Global symbol "$owner_toggle" requires explicit package name at /usr/lib/perl5/vendor_perl/Immunix/SubDomain.pm line 923. Global symbol "$owner_toggle" requires explicit package name at /usr/lib/perl5/vendor_perl/Immunix/SubDomain.pm line 924. Compilation failed in require at /usr/lib/YaST2/servers_non_y2/ag_subdomain line 26. BEGIN failed--compilation aborted at /usr/lib/YaST2/servers_non_y2/ag_subdomain line 26 (#1) (F) You've said "use strict" or "use strict vars", which indicates that all variables must either be lexically scoped (using "my" or "state"), declared beforehand using "our", or explicitly qualified to say which package the global variable is in (using "::"). Uncaught exception from user code: Global symbol "$owner_toggle" requires explicit package name at /usr/lib/perl5/vendor_perl/Immunix/SubDomain.pm line 923. Global symbol "$owner_toggle" requires explicit package name at /usr/lib/perl5/vendor_perl/Immunix/SubDomain.pm line 924. Compilation failed in require at /usr/lib/YaST2/servers_non_y2/ag_subdomain line 26. BEGIN failed--compilation aborted at /usr/lib/YaST2/servers_non_y2/ag_subdomain line 26. at /usr/lib/YaST2/servers_non_y2/ag_subdomain line 26 Global symbol "$owner_toggle" requires explicit package name at /usr/lib/perl5/vendor_perl/Immunix/SubDomain.pm line 923. Global symbol "$owner_toggle" requires explicit package name at /usr/lib/perl5/vendor_perl/Immunix/SubDomain.pm line 924. Compilation failed in require at /usr/lib/YaST2/servers_non_y2/ag_subdomain_profiles line 25. BEGIN failed--compilation aborted at /usr/lib/YaST2/servers_non_y2/ag_subdomain_profiles line 25 (#1) (F) You've said "use strict" or "use strict vars", which indicates that all variables must either be lexically scoped (using "my" or "state"), declared beforehand using "our", or explicitly qualified to say which package the global variable is in (using "::"). Uncaught exception from user code: Global symbol "$owner_toggle" requires explicit package name at /usr/lib/perl5/vendor_perl/Immunix/SubDomain.pm line 923. Global symbol "$owner_toggle" requires explicit package name at /usr/lib/perl5/vendor_perl/Immunix/SubDomain.pm line 924. Compilation failed in require at /usr/lib/YaST2/servers_non_y2/ag_subdomain_profiles line 25. BEGIN failed--compilation aborted at /usr/lib/YaST2/servers_non_y2/ag_subdomain_profiles line 25. at /usr/lib/YaST2/servers_non_y2/ag_subdomain_profiles line 25
This looks very much like dupe (as it is reported against RC1, judging also from error msgs). I'm going to make not-so-verbose Y2ProgramComponent a separate bug *** This bug has been marked as a duplicate of bug 396339 ***