Studio controls hangs forever on "adding bridges"

Bug #1952949 reported by Henning Sprang
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
studio-controls (Ubuntu)
Fix Released
Undecided
Len Ovens

Bug Description

I want to user studio-controls to run my jackd.

But when doing that, Jack seems to start basically, but eventially it's status is displayed as "adding bridges" - and this doesn't change even after minutes of waiting.

I have turned off any type of bridging - no midi, no pulse audio etc, so for one thing it's unclear what bridhges are to be added, and also why it hangs forever.

I could not find any logfiles that give me any further information what's happening, running studio-controls in the terminal also doesnt show more information.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: studio-controls 2.2.8-0ubuntu0.21.10.1
ProcVersionSignature: Ubuntu 5.13.0-21.21-lowlatency 5.13.18
Uname: Linux 5.13.0-21-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec 1 20:01:51 2021
InstallationDate: Installed on 2020-04-12 (597 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
PackageArchitecture: all
SourcePackage: studio-controls
UpgradeStatus: Upgraded to impish on 2021-11-14 (16 days ago)

Revision history for this message
Henning Sprang (henning) wrote :
Changed in studio-controls (Ubuntu):
assignee: nobody → Len Ovens (len-ovenwerks)
Revision history for this message
Len Ovens (len-ovenwerks) wrote :

Please attach the output of convert-studio-controls run on the command line. (first suspect)

Also, from the studio-controls GUI please set System Tweaks-> Logging level to extra, then do a "Start or restart JACK". After that please attach a copy of ~/.log/autojack.log and
~/.log/autojack.log.1 (if the .1 exists)

Changed in studio-controls (Ubuntu):
status: New → Incomplete
Revision history for this message
Henning Sprang (henning) wrote :

here's the autojack.log - didn't know about that file...

There are actually some interesting exceptions.

Revision history for this message
Henning Sprang (henning) wrote :

And the output of convert-studio-controls:

Convert Studio Conrols Config File (version 2.2.8)
Search for: /home/henning/.config/autojack/autojack.json force: False
config file found, check it
checking config file for compatability with version 2.2.8
checking data base
Checking Devices
 Devices checked, continue data base check
write new config file

Changed in studio-controls (Ubuntu):
status: Incomplete → Triaged
Revision history for this message
Len Ovens (len-ovenwerks) wrote :

This was fixed in 2.2.9

Changed in studio-controls (Ubuntu):
status: Triaged → Fix Released
Revision history for this message
Gavin Cannizzaro (gavinpc) wrote :

I also experience this symptom, though maybe from a different cause.

Studio Controls gets stuck on "Adding Bridges", at which point the tail of ~/.log/autojack.log looks like

2022-06-14 16:30:34,767 - AutoJack - INFO - Got start signal.
2022-06-14 16:30:34,767 - AutoJack - INFO - Running: config_start()
2022-06-14 16:30:37,321 - AutoJack - INFO - Running: config_start after jack_stat
2022-06-14 16:30:55,830 - AutoJack - ERROR - Exception in handler for D-Bus signal:
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/dbus/connection.py", line 232, in maybe_handle_message
    self._handler(*args, **kwargs)
  File "/usr/bin/autojack", line 1739, in ses_cb_command
    config_start()
  File "/usr/bin/autojack", line 819, in config_start
    extra_devices()
  File "/usr/bin/autojack", line 142, in extra_devices
    start_slave(fullname)
  File "/usr/bin/autojack", line 1364, in start_slave
    dsr = sub_db['frame']['rate']
TypeError: 'int' object is not subscriptable

I take this to mean that either `sub_db` or `sub_db['frame']` has an int value where a dict is expected.

I am running Studio Controls version 2.3.4 on Ubuntu 22.04.

Revision history for this message
Erich Eickmeyer (eeickmeyer) wrote :

Please don't necro-bump old bugs, file new bug reports.

Revision history for this message
Len Ovens (len-ovenwerks) wrote :

Also this is fixed already in 2.3.5

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.