FS#68857 - [wireplumber] segfault

Attached to Project: Community Packages
Opened by mattia (nTia89) - Saturday, 05 December 2020, 10:07 GMT
Last edited by David Runge (dvzrv) - Wednesday, 26 May 2021, 17:10 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To David Runge (dvzrv)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description:
cannot start wireplumber

Additional info:
* wireplumber 0.3.0-1

Steps to reproduce:
$ wireplumber

Output:
W 10:00:38.490182 pw ../pipewire/src/pipewire/core.c:71:core_event_error: core 0x5559febf9800: proxy 0x5559feccbaf0 id:3: bound:-1 seq:3 res:-2 (No such file or directory) msg:"can't create device: No such file or directory"
W 10:00:38.490372 m-device-activatio ../modules/module-device-activation.c:98:on_node_added: <WpDeviceActivation:0x5559fec49590> cannot find device for node reservation data
W 10:00:38.490387 m-device-activatio ../modules/module-device-activation.c:98:on_node_added: <WpDeviceActivation:0x5559fec49590> cannot find device for node reservation data
W 10:00:38.490401 m-device-activatio ../modules/module-device-activation.c:98:on_node_added: <WpDeviceActivation:0x5559fec49590> cannot find device for node reservation data
W 10:00:38.490413 m-device-activatio ../modules/module-device-activation.c:98:on_node_added: <WpDeviceActivation:0x5559fec49590> cannot find device for node reservation data
W 10:00:38.491522 m-device-activatio ../modules/module-device-activation.c:98:on_node_added: <WpDeviceActivation:0x5559fec49590> cannot find device for node reservation data
C 10:00:38.491910 wp-spa-pod (null):(null):(null): file ../lib/wp/spa-pod.c: line 2421 (wp_spa_pod_parser_new_object): should not be reached
Segmentation fault (core dumped)
This task depends upon

Closed by  David Runge (dvzrv)
Wednesday, 26 May 2021, 17:10 GMT
Reason for closing:  Works for me
Additional comments about closing:  There have been substantial changes to the project upstream.
If the problems persist, please open a new ticket.
Comment by David Runge (dvzrv) - Sunday, 28 February 2021, 14:17 GMT
@nTia89: I believe this is an upstream bug, that was probably introduced by changes to pipewire.

Please report this upstream.

Loading...