Jackd does not see USB device after seconnd connect

Bug #1967615 reported by Ilya Kitaev
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
jackd-defaults (Ubuntu)
New
Undecided
Unassigned

Bug Description

$ uname -a
Linux 5.15.32-051532-generic #202203280440 SMP Mon Mar 28 09:09:36 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

$ cat /etc/issue
Ubuntu 21.10 \n \l

$ jackd --version
jackdmp version 1.9.19 tmpdir /dev/shm protocol 9

I connect any USB device after reboot and it works fine. After reconnect ALSA shows the device but it does not appeared in Carla (ant qjackctl). I have to reboot to use device.

For example

$ aplay -l
**** List of PLAYBACK Hardware Devices ****
...
card 3: H1n [H1n], device 0: USB Audio [USB Audio]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

dmesg:
[ 1105.833466] usb 2-2: new high-speed USB device number 8 using ehci-pci
[ 1108.313496] usb 5-2: new full-speed USB device number 6 using ohci-pci
[ 1108.514438] usb 5-2: New USB device found, idVendor=1686, idProduct=03f5, bcdDevice= 0.00
[ 1108.514450] usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1108.514456] usb 5-2: Product: H1n
[ 1108.514461] usb 5-2: Manufacturer: ZOOM Corporation
[ 1108.514465] usb 5-2: SerialNumber: 000000000000

syslog:

kernel: usb 2-2: new high-speed USB device number 8 using ehci-pci
kernel: usb 5-2: new full-speed USB device number 6 using ohci-pci
kernel: usb 5-2: New USB device found, idVendor=1686, idProduct=03f5, bcdDevice= 0.00
kernel: usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
kernel: usb 5-2: Product: H1n
kernel: usb 5-2: Manufacturer: ZOOM Corporation
kernel: usb 5-2: SerialNumber: 000000000000
mtp-probe[9931]: checking bus 5, device 6: "/sys/devices/pci0000:00/0000:00:13.0/usb5/5-2"
mtp-probe[9931]: bus: 5, device: 6 was not an MTP device
mtp-probe[9943]: checking bus 5, device 6: "/sys/devices/pci0000:00/0000:00:13.0/usb5/5-2"
mtp-probe[9943]: bus: 5, device: 6 was not an MTP device

This started after upgraded to 21.10 from 20.04

Tags: kinetic
Revision history for this message
Ilya Kitaev (ilya-kitaev) wrote :

The same thing with Behringer UMC404

Revision history for this message
CharlesA (charlesa) wrote :

Assigning this to Ubuntu, not UbuntuForums, as this is not a forums issue.

affects: ubuntuforums.org → ubuntu
Revision history for this message
Paul White (paulw2u) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner.

Ubuntu 21.10 (impish) reached end-of-life on July 14, 2022.

Is this still an issue when using a currently supported release of Ubuntu? If so, please execute the following command only once, as it will automatically gather debugging information, in a terminal:

  apport-collect 1967615

and then change the status of the bug back to 'New'.

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

affects: ubuntu → jackd-defaults (Ubuntu)
Changed in jackd-defaults (Ubuntu):
status: New → Incomplete
tags: added: impish
Revision history for this message
Ilya Kitaev (ilya-kitaev) wrote :

Hi. Same issue in 22.10

$ uname -a
Linux darkhorse 6.0.19-060019-generic #202301120739 SMP PREEMPT_DYNAMIC Thu Jan 12 13:28:53 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

$ cat /etc/issue
Ubuntu 22.10 \n \l

$ jackd --version
jackdmp version 1.9.21 tmpdir /dev/shm protocol 9

Sometime devices (after several unplugs and plugs) present only in Alsa, but jackd (Carla) does not see them. No errors in logs.

Revision history for this message
Ilya Kitaev (ilya-kitaev) wrote :

But interesting thing is that MiDi controller present in jackd although soundcard (audio ports) not

Paul White (paulw2u)
tags: added: kinetic
removed: impish
Changed in jackd-defaults (Ubuntu):
status: Incomplete → New
Revision history for this message
Ilya Kitaev (ilya-kitaev) wrote :

I got this errors when devices is appears and everythong is ok:

Sat Mar 11 00:50:27 2023: ERROR: JackEngine::XRun: client = a2j was not finished, state = Triggered
Sat Mar 11 00:50:27 2023: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Sat Mar 11 00:50:27 2023: ERROR: JackEngine::XRun: client = a2j was not finished, state = Triggered
Sat Mar 11 00:50:27 2023: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Sat Mar 11 00:50:27 2023: ERROR: JackEngine::XRun: client = a2j was not finished, state = Triggered
Sat Mar 11 00:50:27 2023: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Sat Mar 11 00:50:31 2023: New client 'USB3,0,0-out' with PID 74471
Sat Mar 11 00:50:32 2023: New client 'USB3,0,0-in' with PID 74472

And this when not:

Sat Mar 11 00:48:27 2023: ERROR: JackEngine::XRun: client = pulse_in was not finished, state = Triggered
Sat Mar 11 00:48:27 2023: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Sat Mar 11 00:48:27 2023: ERROR: JackEngine::XRun: client = pulse_in was not finished, state = Triggered
Sat Mar 11 00:48:27 2023: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Sat Mar 11 00:48:28 2023: ERROR: JackEngine::XRun: client = pulse_in was not finished, state = Triggered
Sat Mar 11 00:48:28 2023: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Sat Mar 11 00:48:28 2023: ERROR: JackEngine::XRun: client = pulse_in was not finished, state = Triggered
Sat Mar 11 00:48:28 2023: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error

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.