[Touch-packages] [Bug 2099990] Re: lsusb fails due to apparmor
So could be that there was a change in past years (not done by hand) and installing the new apparmor the old config of lsusb got a .save extension and the new one was installed without flags=(complain), and this caused the problem. Making the hand change i did yesterday just solved partially the problem then... The Strange part is that i don't remember of changing anything in apparmor in the past.. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/200 Title: lsusb fails due to apparmor Status in apparmor package in Ubuntu: Fix Released Bug description: With apparmor 4.1.0~beta5-0ubuntu5 on a RISC-V Microchip Icicle Kit I see that the kernel discovers USB: [ +0.008662] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ +0.007425] usb 1-1: Product: Ultra [ +0.003688] usb 1-1: Manufacturer: SanDisk [ +0.004245] usb 1-1: SerialNumber: 010187b422912d2f128c699458cec5c82b7af2ece2713972b09d1de68f741b2afecb66a842d0ff9957008a558107452c91e7 [ +0.011662] usb-storage 1-1:1.0: USB Mass Storage device detected [ +0.012149] scsi host0: usb-storage 1-1:1.0 [ +0.011826] usbcore: registered new interface driver usb-storage [ +0.035775] usbcore: registered new interface driver uas But lsusb shows not device. Looking as journalctl shows that apparmor is blocking: Feb 25 12:46:58 ubuntu sudo[1508]: pam_unix(sudo:session): session opened for user root(uid=0) by ubuntu(uid=1000) Feb 25 12:46:58 ubuntu kernel: audit: type=1400 audit(1740487618.039:207): apparmor="DENIED" operation="capable" class="cap" profile="lsusb" pid=1510 comm="lsusb" capability=12 capname="net_admin" Feb 25 12:46:58 ubuntu kernel: audit: type=1400 audit(1740487618.039:208): apparmor="DENIED" operation="open" class="file" profile="lsusb" name="/sys/devices/platform/soc/20201000.usb/musb-hdrc.2.auto/usb1/uevent" pid=1510 comm="lsusb" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Feb 25 12:46:58 ubuntu kernel: audit: type=1400 audit(1740487618.043:209): apparmor="DENIED" operation="open" class="file" profile="lsusb" name="/sys/devices/platform/soc/20201000.usb/musb-hdrc.2.auto/usb1/1-1/uevent" pid=1510 comm="lsusb" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Feb 25 12:46:58 ubuntu kernel: audit: type=1400 audit(1740487618.043:210): apparmor="DENIED" operation="open" class="file" profile="lsusb" name="/sys/devices/platform/soc/20201000.usb/musb-hdrc.2.auto/usb1/1-0:1.0/uevent" pid=1510 comm="lsusb" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Feb 25 12:46:58 ubuntu kernel: audit: type=1400 audit(1740487618.047:211): apparmor="DENIED" operation="open" class="file" profile="lsusb" name="/sys/devices/platform/soc/20201000.usb/musb-hdrc.2.auto/usb1/1-1/1-1:1.0/uevent" pid=1510 comm="lsusb" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Feb 25 12:46:58 ubuntu sudo[1508]: pam_unix(sudo:session): session closed for user root /etc/apparmor.d/usr.bin.lsusb does not exist. sudo apparmor_status shows that lsusb is in enforce mode. Only after putting /usb/bin/lsusb into complain mode the command starts to work. Best regards Heinrich --- ProblemType: Bug ApportVersion: 2.31.0+git20250220-0ubuntu2 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20250225 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) DistroRelease: Ubuntu 25.04 Package: apparmor 4.1.0~beta5-0ubuntu5 PackageArchitecture: riscv64 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=vt220 ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-6.14.0-4-generic root=UUID=d7adaa9d-66b4-4ce4-a45f-3651ae4bbb85 ro efi=debug earlycon=sbi sysctl.kernel.watchdog_thresh=60 ProcVersionSignature: Ubuntu 6.14.0-4.4.1~1-generic 6.14.0-rc3 Syslog: 2025-02-25T12:34:08.711312+00:00 ubuntu dbus-daemon[909]: [system] AppArmor D-Bus mediation is enabled Tags: cloud-image plucky Uname: Linux 6.14.0-4-generic riscv64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True mtime.conffile..etc.apparmor.d.lsusb: 2025-02-25T12:57:31.410467 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/200/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2099990] Re: lsusb fails due to apparmor
Hi, Installed plucky yesterday , and had the same problem, i was looking for aa-compalin command to set complain mode to lsusb but command was not installed (strange because other aa- was ok) but at last i had a manual look in the apparmor.d folder and i saw lsub and lsusb.save ! Looking inside the two configs i saw that the lsusb.save file was containing the complain option and in the lsusb no. so deleted lsusb and renamed the lsusb.save to lsusb. Solved the problem. Maybe installing the new version of apparmor created a new lsusb profile and old profile renamed as .save thanks for your suggestions anyway -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/200 Title: lsusb fails due to apparmor Status in apparmor package in Ubuntu: Fix Released Bug description: With apparmor 4.1.0~beta5-0ubuntu5 on a RISC-V Microchip Icicle Kit I see that the kernel discovers USB: [ +0.008662] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ +0.007425] usb 1-1: Product: Ultra [ +0.003688] usb 1-1: Manufacturer: SanDisk [ +0.004245] usb 1-1: SerialNumber: 010187b422912d2f128c699458cec5c82b7af2ece2713972b09d1de68f741b2afecb66a842d0ff9957008a558107452c91e7 [ +0.011662] usb-storage 1-1:1.0: USB Mass Storage device detected [ +0.012149] scsi host0: usb-storage 1-1:1.0 [ +0.011826] usbcore: registered new interface driver usb-storage [ +0.035775] usbcore: registered new interface driver uas But lsusb shows not device. Looking as journalctl shows that apparmor is blocking: Feb 25 12:46:58 ubuntu sudo[1508]: pam_unix(sudo:session): session opened for user root(uid=0) by ubuntu(uid=1000) Feb 25 12:46:58 ubuntu kernel: audit: type=1400 audit(1740487618.039:207): apparmor="DENIED" operation="capable" class="cap" profile="lsusb" pid=1510 comm="lsusb" capability=12 capname="net_admin" Feb 25 12:46:58 ubuntu kernel: audit: type=1400 audit(1740487618.039:208): apparmor="DENIED" operation="open" class="file" profile="lsusb" name="/sys/devices/platform/soc/20201000.usb/musb-hdrc.2.auto/usb1/uevent" pid=1510 comm="lsusb" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Feb 25 12:46:58 ubuntu kernel: audit: type=1400 audit(1740487618.043:209): apparmor="DENIED" operation="open" class="file" profile="lsusb" name="/sys/devices/platform/soc/20201000.usb/musb-hdrc.2.auto/usb1/1-1/uevent" pid=1510 comm="lsusb" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Feb 25 12:46:58 ubuntu kernel: audit: type=1400 audit(1740487618.043:210): apparmor="DENIED" operation="open" class="file" profile="lsusb" name="/sys/devices/platform/soc/20201000.usb/musb-hdrc.2.auto/usb1/1-0:1.0/uevent" pid=1510 comm="lsusb" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Feb 25 12:46:58 ubuntu kernel: audit: type=1400 audit(1740487618.047:211): apparmor="DENIED" operation="open" class="file" profile="lsusb" name="/sys/devices/platform/soc/20201000.usb/musb-hdrc.2.auto/usb1/1-1/1-1:1.0/uevent" pid=1510 comm="lsusb" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Feb 25 12:46:58 ubuntu sudo[1508]: pam_unix(sudo:session): session closed for user root /etc/apparmor.d/usr.bin.lsusb does not exist. sudo apparmor_status shows that lsusb is in enforce mode. Only after putting /usb/bin/lsusb into complain mode the command starts to work. Best regards Heinrich --- ProblemType: Bug ApportVersion: 2.31.0+git20250220-0ubuntu2 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20250225 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) DistroRelease: Ubuntu 25.04 Package: apparmor 4.1.0~beta5-0ubuntu5 PackageArchitecture: riscv64 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=vt220 ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-6.14.0-4-generic root=UUID=d7adaa9d-66b4-4ce4-a45f-3651ae4bbb85 ro efi=debug earlycon=sbi sysctl.kernel.watchdog_thresh=60 ProcVersionSignature: Ubuntu 6.14.0-4.4.1~1-generic 6.14.0-rc3 Syslog: 2025-02-25T12:34:08.711312+00:00 ubuntu dbus-daemon[909]: [system] AppArmor D-Bus mediation is enabled Tags: cloud-image plucky Uname: Linux 6.14.0-4-generic riscv64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True mtime.conffile..etc.apparmor.d.lsusb: 2025-02-25T12:57:31.410467 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/200/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2099990] Re: lsusb fails due to apparmor
Installed apparmor-utils package and aa-complain is ok now. But i never did editing in apparmor.d files before yesterday, and on 24.04 lsusb was not complaining. After upgrading to 25.04 it started the problem. So really strange to have a .save file if no one has edited anything neither before or later. For me it's solved and closed anyway. But the cause of extra .save file is not derivated from a local edit, must be somewhere else. Let's see if someone else has this prob, otherwise just close. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/200 Title: lsusb fails due to apparmor Status in apparmor package in Ubuntu: Fix Released Bug description: With apparmor 4.1.0~beta5-0ubuntu5 on a RISC-V Microchip Icicle Kit I see that the kernel discovers USB: [ +0.008662] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ +0.007425] usb 1-1: Product: Ultra [ +0.003688] usb 1-1: Manufacturer: SanDisk [ +0.004245] usb 1-1: SerialNumber: 010187b422912d2f128c699458cec5c82b7af2ece2713972b09d1de68f741b2afecb66a842d0ff9957008a558107452c91e7 [ +0.011662] usb-storage 1-1:1.0: USB Mass Storage device detected [ +0.012149] scsi host0: usb-storage 1-1:1.0 [ +0.011826] usbcore: registered new interface driver usb-storage [ +0.035775] usbcore: registered new interface driver uas But lsusb shows not device. Looking as journalctl shows that apparmor is blocking: Feb 25 12:46:58 ubuntu sudo[1508]: pam_unix(sudo:session): session opened for user root(uid=0) by ubuntu(uid=1000) Feb 25 12:46:58 ubuntu kernel: audit: type=1400 audit(1740487618.039:207): apparmor="DENIED" operation="capable" class="cap" profile="lsusb" pid=1510 comm="lsusb" capability=12 capname="net_admin" Feb 25 12:46:58 ubuntu kernel: audit: type=1400 audit(1740487618.039:208): apparmor="DENIED" operation="open" class="file" profile="lsusb" name="/sys/devices/platform/soc/20201000.usb/musb-hdrc.2.auto/usb1/uevent" pid=1510 comm="lsusb" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Feb 25 12:46:58 ubuntu kernel: audit: type=1400 audit(1740487618.043:209): apparmor="DENIED" operation="open" class="file" profile="lsusb" name="/sys/devices/platform/soc/20201000.usb/musb-hdrc.2.auto/usb1/1-1/uevent" pid=1510 comm="lsusb" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Feb 25 12:46:58 ubuntu kernel: audit: type=1400 audit(1740487618.043:210): apparmor="DENIED" operation="open" class="file" profile="lsusb" name="/sys/devices/platform/soc/20201000.usb/musb-hdrc.2.auto/usb1/1-0:1.0/uevent" pid=1510 comm="lsusb" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Feb 25 12:46:58 ubuntu kernel: audit: type=1400 audit(1740487618.047:211): apparmor="DENIED" operation="open" class="file" profile="lsusb" name="/sys/devices/platform/soc/20201000.usb/musb-hdrc.2.auto/usb1/1-1/1-1:1.0/uevent" pid=1510 comm="lsusb" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Feb 25 12:46:58 ubuntu sudo[1508]: pam_unix(sudo:session): session closed for user root /etc/apparmor.d/usr.bin.lsusb does not exist. sudo apparmor_status shows that lsusb is in enforce mode. Only after putting /usb/bin/lsusb into complain mode the command starts to work. Best regards Heinrich --- ProblemType: Bug ApportVersion: 2.31.0+git20250220-0ubuntu2 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20250225 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) DistroRelease: Ubuntu 25.04 Package: apparmor 4.1.0~beta5-0ubuntu5 PackageArchitecture: riscv64 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=vt220 ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-6.14.0-4-generic root=UUID=d7adaa9d-66b4-4ce4-a45f-3651ae4bbb85 ro efi=debug earlycon=sbi sysctl.kernel.watchdog_thresh=60 ProcVersionSignature: Ubuntu 6.14.0-4.4.1~1-generic 6.14.0-rc3 Syslog: 2025-02-25T12:34:08.711312+00:00 ubuntu dbus-daemon[909]: [system] AppArmor D-Bus mediation is enabled Tags: cloud-image plucky Uname: Linux 6.14.0-4-generic riscv64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True mtime.conffile..etc.apparmor.d.lsusb: 2025-02-25T12:57:31.410467 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/200/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
