** Description changed:

  [ Impact ]
  
  iotop-c failed to launch at all due to permission denials in nl_init and
- missing capabilities in the iotop-c profile.
+ missing capabilities in the iotop-c profile. Even after granting iotop-c
+ the permissions required for nl_init to succeed, it was still missing
+ the permissions required to re-nice processes.
  
  [ Test Plan ]
  
-  * Launch iotop-c under sudo (make sure to invoke iotop-c directly instead of 
iotop, which might be symlinked to the distinct iotop-py)
-    - Without the fix: iotop-c fails to launch due to permission denials in 
nl_init
-    - With the fix: iotop-c should launch successfully
-  * Attempt to set the ionice value of a running process using iotop-c, and 
verify that the operation succeeds
+  * Launch iotop-c under sudo (make sure to invoke iotop-c directly instead of 
iotop, which might be symlinked to the distinct iotop-py)
+    - Without the fix: iotop-c fails to launch due to permission denials in 
nl_init
+    - With the fix: iotop-c should launch successfully
+  * Attempt to set the ionice value of a running process using iotop-c, and 
verify that the operation succeeds
  
  [ Where problems could occur ]
  
  The additions to the iotop-c profile are loosening confinement on a
  profile. However, if a user manually modified the installed profiles,
  then the package upgrade would cause conflicts, and rejection of the
  incoming changes (either by hand during an interactive upgrade or
  automatically during an batch unattended upgrade) would result in end
  users not getting the packaged fix.
  
  [ Other Info ]
  
  --------Original bug description
  
  On a fresh installation of Kubuntu 25.04 in VirtualBox
  Installation of packages 1.26-1, 1.27-1 and 1.28-1 work, but program iotop-c 
does not start due to insufficient rights with output:
  nl_init: insufficient rights
  
  Interestingly, all three packages work on Kubuntu 24.10
  Therefore, this appears to be a problem with the underlying operating system.

** Description changed:

  [ Impact ]
  
  iotop-c failed to launch at all due to permission denials in nl_init and
  missing capabilities in the iotop-c profile. Even after granting iotop-c
  the permissions required for nl_init to succeed, it was still missing
  the permissions required to re-nice processes.
  
  [ Test Plan ]
  
+  * Run `sudo aa-status` and verify that an iotop-c profile is loaded
   * Launch iotop-c under sudo (make sure to invoke iotop-c directly instead of 
iotop, which might be symlinked to the distinct iotop-py)
     - Without the fix: iotop-c fails to launch due to permission denials in 
nl_init
     - With the fix: iotop-c should launch successfully
   * Attempt to set the ionice value of a running process using iotop-c, and 
verify that the operation succeeds
  
  [ Where problems could occur ]
  
  The additions to the iotop-c profile are loosening confinement on a
  profile. However, if a user manually modified the installed profiles,
  then the package upgrade would cause conflicts, and rejection of the
  incoming changes (either by hand during an interactive upgrade or
  automatically during an batch unattended upgrade) would result in end
  users not getting the packaged fix.
  
  [ Other Info ]
  
  --------Original bug description
  
  On a fresh installation of Kubuntu 25.04 in VirtualBox
  Installation of packages 1.26-1, 1.27-1 and 1.28-1 work, but program iotop-c 
does not start due to insufficient rights with output:
  nl_init: insufficient rights
  
  Interestingly, all three packages work on Kubuntu 24.10
  Therefore, this appears to be a problem with the underlying operating system.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2107727

Title:
  iotop-c: Call of nl_init fails due to insufficient rights

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2107727/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to