Skip to content

pavucontrol X Window System error "The error was 'BadIDChoice (invalid resource ID chosen for this connection)'" #28

@janvda

Description

@janvda

After the upgrade to balena host os version 2.43.0+rev1: the service pulseaudio-client-tcp reported the following error for test_id = 3 (= pavucontrol)

05.10.19 17:01:28 (+0200)  pulseaudio-client-tcp  launching pavucontrol ...
05.10.19 17:01:55 (+0200)  pulseaudio-client-tcp  
05.10.19 17:01:55 (+0200)  pulseaudio-client-tcp  (pavucontrol:24): Gdk-ERROR **: 15:01:55.067: The program 'pavucontrol' received an X Window System error.
05.10.19 17:01:55 (+0200)  pulseaudio-client-tcp  This probably reflects a bug in the program.
05.10.19 17:01:55 (+0200)  pulseaudio-client-tcp  The error was 'BadIDChoice (invalid resource ID chosen for this connection)'.
05.10.19 17:01:55 (+0200)  pulseaudio-client-tcp    (Details: serial 24992 error_code 14 request_code 53 (core protocol) minor_code 0)
05.10.19 17:01:55 (+0200)  pulseaudio-client-tcp    (Note to programmers: normally, X errors are reported asynchronously;
05.10.19 17:01:55 (+0200)  pulseaudio-client-tcp     that is, you will receive the error a while after causing it.
05.10.19 17:01:55 (+0200)  pulseaudio-client-tcp     To debug your program, run it with the GDK_SYNCHRONIZE environment
05.10.19 17:01:55 (+0200)  pulseaudio-client-tcp     variable to change this behavior. You can then get a meaningful
05.10.19 17:01:55 (+0200)  pulseaudio-client-tcp     backtrace from your debugger if you break on the gdk_x_error() function.)
05.10.19 17:01:58 (+0200)  pulseaudio-client-tcp  ./start.sh: line 43:    24 Trace/breakpoint trap   (core dumped) DISPLAY=$remote_display pavucontrol
05.10.19 17:01:58 (+0200)  pulseaudio-client-tcp  sleeping forever ...

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions