[Bug 1965439] Re: Driver manager KCM can no longer launch

Erich Eickmeyer  1965439 at bugs.launchpad.net
Tue Apr 5 16:30:51 UTC 2022

This seems to be a bigger bug and applies to software-properties-qt and
perhaps pkexec. As it turns out, one cannot launch "sofware-properties-
qt" from within plasma-discover either. Even though it calls pkexec to
launch it, it fails every time even if the user is a system admin.

** Changed in: ubuntustudio-default-settings (Ubuntu Jammy)
       Status: Fix Released => In Progress

** Summary changed:

- Driver manager KCM can no longer launch
+ software-properties-qt can no longer launch

** Summary changed:

- software-properties-qt can no longer launch
+ software-properties-qt can no longer launch when called by pkexec

** Also affects: software-properties (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: policykit-1 (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: policykit-1 (Ubuntu Jammy)
       Status: New => Confirmed

** Changed in: software-properties (Ubuntu Jammy)
       Status: New => Confirmed

** Changed in: policykit-1 (Ubuntu Jammy)
   Importance: Undecided => Critical

** Changed in: software-properties (Ubuntu Jammy)
   Importance: Undecided => Critical

** Changed in: ubuntustudio-default-settings (Ubuntu Jammy)
   Importance: Critical => High

** Changed in: kubuntu-settings (Ubuntu Jammy)
   Importance: Undecided => High

** Description changed:

+ See description below. As the driver manager is done inside software-
+ properties-qt, it's basically the same bug, but now it's affected by
+ something we can't exactly get into the mechanism of: plasma-discover's
+ "Software Sources" link.
+ Earlier description:
  The driver manager for both Ubuntu Studio and Kubuntu can no longer
  launch due to some updated security measures in PolicyKit.
  The original behavior was that systemsettings would open
  /usr/bin/ubuntustudio-driver-manager (or /usr/bin/kubuntu-driver-manger)
  via pkexec, which would then open software-settings-qt. Unfortunately,
  the new behavior does not act correctly to pkexec and pkexec does not
  see the user as available in the sudoers file.
  The only way around this was to pass "export DISPLAY=:0" inside the
  appropriate driver manager executable with the command "sudo software-
  properties-qt". The KCM itself needs to execute the driver-manager via
  xterm, which then prompts for a password. It's ugly, but it works.
  I will attach a debdiff for the kubuntu-settings package.
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntustudio-default-settings 22.04.19 [modified: usr/share/sddm/themes/ubuntustudio/theme.conf]
  ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19
  Uname: Linux 5.15.0-22-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Mar 17 12:19:44 2022
  InstallationDate: Installed on 2021-03-20 (361 days ago)
  InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320)
  PackageArchitecture: all
  SourcePackage: ubuntustudio-default-settings
  UpgradeStatus: Upgraded to jammy on 2021-11-07 (130 days ago)
  modified.conffile..etc.skel..local.share.konsole.Profile: [deleted]

You received this bug notification because you are a member of Ubuntu
Studio Development, which is subscribed to ubuntustudio-default-settings
in Ubuntu.

  software-properties-qt can no longer launch when called by pkexec

To manage notifications about this bug go to:

More information about the Ubuntu-reviews mailing list