WiFi and USB problems with AppArmor 5

English Install/Boot/Login
1

Hi,

This is basically a duplicate of my mail list thread for visibility.

After Tumbleweed update to snapshot 20260514, which has AppArmor 5 my WiFi
stopped working.

<error> [1778917266.6687] device (wlp9s0): Couldn't initialize supplicant 
interface: Failed to D-Bus activate wpa_supplicant service

Also lsusb shows only error “unable to initialize usb spec”.

Disabling AppArmor (sudo systemctl disable apparmor.service) and rebooting
solves these issues, but kinda isn’t very good solution.

Any advise?

2 Likes
2

https://bugzilla.opensuse.org/show_bug.cgi?id=1265377
https://bugzilla.opensuse.org/show_bug.cgi?id=1265380

Downgrade the apparmor packages to the 4.7 version. Get the rpms from the TW history repos.
I downgraded the packages at the affected machine and locked the packages. For this solution you need another box with internet connection, to download all apparmor rpm to an USB stick.

Or use the temporary solution from the second bugreport.

2 Likes
3

Which packages specifically? This is all I’m seeing:

akonadi-apparmor-26.04.0-1.2.x86_64.rpm
akonadi-apparmor-26.04.1-1.1.x86_64.rpm
apache2-mod_apparmor-4.1.7-1.3.x86_64.rpm
apache2-mod_apparmor-5.0.0-1.1.x86_64.rpm
apparmor-parser-4.1.7-1.3.x86_64.rpm
apparmor-parser-5.0.0-1.1.x86_64.rpm
libapparmor-devel-4.1.7-1.2.x86_64.rpm
libapparmor-devel-5.0.0-1.1.x86_64.rpm
libapparmor1-4.1.7-1.2.x86_64.rpm
libapparmor1-5.0.0-1.1.x86_64.rpm
libapparmor1-32bit-4.1.7-1.2.x86_64.rpm
libapparmor1-32bit-5.0.0-1.1.x86_64.rpm
lutris-apparmor-0.5.22-1.1.x86_64.rpm
lutris-apparmor-0.5.22-2.1.x86_64.rpm
pam_apparmor-4.1.7-1.3.x86_64.rpm
pam_apparmor-5.0.0-1.1.x86_64.rpm
pam_apparmor-32bit-4.1.7-1.3.x86_64.rpm
pam_apparmor-32bit-5.0.0-1.1.x86_64.rpm
patterns-base-apparmor-32bit-20241218-28.1.x86_64.rpm
patterns-base-apparmor-32bit-20241218-29.1.x86_64.rpm
patterns-base-apparmor-20241218-28.1.x86_64.rpm
patterns-base-apparmor-20241218-29.1.x86_64.rpm
perl-apparmor-4.1.7-1.3.x86_64.rpm
perl-apparmor-5.0.0-1.1.x86_64.rpm
python3-apparmor-4.1.7-1.3.x86_64.rpm
python3-apparmor-5.0.0-1.1.x86_64.rpm
ruby-apparmor-4.1.7-1.3.x86_64.rpm
ruby-apparmor-5.0.0-1.1.x86_64.rpm

I can only see 5 (highlighted with * symbol) of the packages I have installed on my system there:

S  | Name                   | Summary                                                             | Type
---+------------------------+---------------------------------------------------------------------+--------
i+ | apparmor                   | AppArmor                                                            | pattern
i+ | apparmor-abstractions      | AppArmor abstractions and directory structure                       | package
i+ | apparmor-docs              | AppArmor Documentation package                                      | package
i+ | **apparmor-parser**        | AppArmor userlevel parser utility                                   | package
i+ | apparmor-profiles          | AppArmor profiles that are loaded into the apparmor kernel module   | package
i+ | apparmor-utils             | AppArmor User-Level Utilities Useful for Creating AppArmor Profiles | package
i+ | **libapparmor1**           | Utility library for AppArmor                                        | package
i  | **lutris-apparmor**        | Apparmor profile for lutris                                         | package
i+ | **patterns-base-apparmor** | AppArmor                                                            | package
i  | plocate-apparmor           | Apparmor profiles for plocate                                       | package
i+ | **python3-apparmor**       | Python 3 interface for libapparmor functions                        | package
i+ | yast2-apparmor             | YaST2 - Plugins for AppArmor Profile Management                     | package
4

Check noarch it contains other packages.
I’ve downgraded these:

sudo zypper in --oldpackage apparmor-abstractions-4.1.7-1.3 apparmor-docs-4.1.7-1.3 apparmor-parser-4.1.7-1.3 apparmor-parser-lang-4.1.7-1.3 apparmor-profiles-4.1.7-1.3 apparmor-utils-4.1.7-1.3 apparmor-utils-lang-4.1.7-1.3 libapparmor-devel-4.1.7-1.2 libapparmor1-4.1.7-1.2 python3-apparmor-4.1.7-1.3
1 Like
5

When searching for installed packages, better use zypper se -si <searchterm>. In this way you will see the package version, and if you find it in the noarch or x86_64 directory on the mirror.

:~> LANG=C zypper se -si apparmor
Loading repository data...
Reading installed packages...

S  | Name                   | Type    | Version       | Arch   | Repository
---+------------------------+---------+---------------+--------+------------------
i+ | apparmor               | pattern | 20241218-29.1 | x86_64 | repo-oss
il | apparmor-abstractions  | package | 4.1.7-1.3     | noarch | (System Packages)
il | apparmor-docs          | package | 4.1.7-1.3     | noarch | (System Packages)
il | apparmor-parser        | package | 4.1.7-1.3     | x86_64 | (System Packages)
il | apparmor-parser-lang   | package | 4.1.7-1.3     | noarch | (System Packages)
il | apparmor-profiles      | package | 4.1.7-1.3     | noarch | (System Packages)
il | apparmor-utils         | package | 4.1.7-1.3     | noarch | (System Packages)
il | apparmor-utils-lang    | package | 4.1.7-1.3     | noarch | (System Packages)
il | libapparmor1           | package | 4.1.7-1.2     | x86_64 | (System Packages)
i+ | patterns-base-apparmor | package | 20241218-29.1 | x86_64 | repo-oss
il | python3-apparmor       | package | 4.1.7-1.3     | x86_64 | (System Packages)
i  | yast2-apparmor         | package | 5.0.1-1.5     | noarch | repo-oss
1 Like
6

Thanks. Forgot about that. These are the packages I ended up installing, and it seems to be working now (had to enable the apparmor service again and rebooted as well to be sure):

sudo zypper in --oldpackage apparmor-abstractions-4.1.7-1.3.noarch.rpm apparmor-docs-4.1.7-1.3.noarch.rpm apparmor-parser-4.1.7-1.3.x86_64.rpm apparmor-profiles-4.1.7-1.3.noarch.rpm apparmor-utils-4.1.7-1.3.noarch.rpm libapparmor1-4.1.7-1.2.x86_64.rpm python3-apparmor-4.1.7-1.3.x86_64.rpm
7

Hello,
for advanced user I have a question, in the bug report they seems to explain that AppArmor will be less tested in the future as SeLinux is the default security system in open suse.
Do we need to migrate ? could it be a solution ?

8

Hello,
for fresh installs, Leap 16 switch default from AppArmor (in previous versions) to SELinux. The entreprise version SUSE Linux Entreprise 16.0 don’t even provide AppArmor any more. I think it’s a good clue about what’s coming next.
Source : Leap 16.0 releases notes, security part.

9

https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/XVFIZAD73POP6PHCFHUECMKIXSYNWCQ7/

10

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.