On Tue, Apr 21, 2020 at 2:04 PM Tollef Fog Heen <tfh...@err.no> wrote:
> ]] Felipe Sateler > > > Could you share the output of `pactl list sinks`? It appears the problem > is not really in the device description. > > Sink #11 > State: IDLE > Name: bluez_sink.EC_66_D1_XX_XX_XX.headset_head_unit > Description: Bowers & Wilkins PX > Driver: module-bluez5-device.c > Sample Specification: s16le 1ch 8000Hz > Channel Map: mono > Owner Module: 31 > Mute: no > Volume: mono: 37987 / 58% > balance 0.00 > Base Volume: 65536 / 100% > Monitor Source: > bluez_sink.EC_66_D1_XX_XX_XX.headset_head_unit.monitor > Latency: 24995 usec, configured 28000 usec > Flags: HARDWARE HW_VOLUME_CTRL LATENCY > Properties: > bluetooth.protocol = "headset_head_unit" > device.intended_roles = "phone" > device.description = "Bowers & Wilkins PX" > device.string = "EC:66:D1:XX:XX:XX" > device.api = "bluez" > device.class = "sound" > device.bus = "bluetooth" > device.form_factor = "headphone" > bluez.path = "/org/bluez/hci0/dev_EC_66_D1_XX_XX_XX" > bluez.class = "0x240418" > bluez.alias = "Bowers & Wilkins PX" > device.icon_name = "audio-headphones-bluetooth" > Ports: > headphone-output: Hovudtelefonar (priority: 0, available) > Active Port: headphone-output > Formats: > pcm > > So, I could not reproduce the issue by setting bluez.alias either. Does the console error happen on applicatin startup? Or when switching to a given tab? -- Saludos, Felipe Sateler