ubuntustudio-bugs team mailing list archive

[Erich Eickmeyer  <1950817@xxxxxxxxxxxxxxxxxx>]

** Tags removed: verification-needed verification-needed-impish
** Tags added: verification-done verification-done-impish

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

Title:
  [SRU] Studio-controls not launching on Ubuntu 21.10, KeyError: 'id'

Status in studio-controls package in Ubuntu:
  Fix Released
Status in studio-controls source package in Impish:
  Fix Committed
Status in studio-controls source package in Jammy:
  Fix Released

Bug description:
  [ Impact ]

  Users in certain edge cases of hardware configurations are running
  into issues where studio-controls is failing to upgrade previous
  configurations and therefore failing to launch. It was found that an
  integer needed to be converted to a string in some cases, and was
  overlooked previously.

  [ Test Plan ]

  Using a system that had been upgraded from 20.04 to 20.10, 21.04, and
  finally 21.10 and having run studio-controls previously with success,
  run studio-controls. In certain hardware configurations, it will crash
  and return invalid key of "id". This is due to an incorrect conversion
  of the old-style configuration to the newer json configuration.

  [ Where problems could occur ]

  While this fixes the issue outlined above, it could cause problems
  where the json file was previously converted correctly, but this is
  unlikely.

  [ Other Information ]

  Original bug report follows:

  
  ---

  Hi,

  I am using studio-controls 2.2.7-0ubuntu1 after having upgraded to
  Impish.  Studio-controls fails to launch with the following traceback:

  install path: /usr
  Config file: /home/steve/.config/autojack/autojack.json
  Traceback (most recent call last):
    File "/usr/bin/studio-controls", line 1837, in <module>
      us = StudioControls()
    File "/usr/bin/studio-controls", line 555, in __init__
      self.devdb.scan_dev(self.conf_db)
    File "/usr/bin/studio-controls", line 164, in scan_dev
      if usb and [ conf['devices'][dev]['id'], conf['devices'][dev]['bus'] ] == [ d_id, bus ]:
  KeyError: 'id'

  Here is my system info:

  Operating System: Kubuntu 21.10
  KDE Plasma Version: 5.22.5
  KDE Frameworks Version: 5.86.0
  Qt Version: 5.15.2
  Kernel Version: 5.13.0-21-lowlatency (64-bit)
  Graphics Platform: X11
  Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz
  Memory: 15.3 GiB of RAM
  Graphics Processor: Mesa Intel® UHD Graphics 620

  I do have the file autojack.json in .config/autojack that is referred
  to in another bug report.

  After failing to launch, I have a studio-controls.lock file created in
  the .config/autojack directory.  The studio-controls interface does
  not appear at any time.

  Last point, I'm using Pipewire, as I was before upgrading to 21.10,
  which didn't create a problem with Studio-controls then.  I would like
  to continue to use Studio-controls to control cpu performance and
  intel boost, and possibly other things.

  Thanks !!

  Stephen
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2020-09-18 (421 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Package: studio-controls 2.2.7-0ubuntu1
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.13.0-21.21-lowlatency 5.13.18
  Tags: impish third-party-packages
  Uname: Linux 5.13.0-21-lowlatency x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-26 (19 days ago)
  UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo www-data
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/studio-controls/+bug/1950817/+subscriptions