Package Details: chordpro-gui 6.090.1-4

Git Clone URL: https://aur.archlinux.org/chordpro-gui.git (read-only, click to copy)
Package Base: chordpro-gui
Description: A lyrics and chords formatting program (CLI and GUI)
Upstream URL: https://chordpro.org/
Keywords: chordpro chords guitar music
Licenses: Artistic-2.0
Conflicts: chordpro
Provides: chordpro
Submitter: joelvaz0x01
Maintainer: joelvaz0x01
Last Packager: joelvaz0x01
Votes: 1
Popularity: 0.001161
First Submitted: 2025-05-20 17:46 (UTC)
Last Updated: 2026-02-25 16:28 (UTC)

Latest Comments

SmileyChris commented on 2026-02-25 21:54 (UTC)

A more efficient workaround, turning off just the DMA-buffer renderer: WEBKIT_DISABLE_DMABUF_RENDERER=1 wxchordpro

SmileyChris commented on 2026-02-25 21:45 (UTC)

Thanks for checking and rebuilding, but still failing for me. I also see others have had the same problem in https://aur.archlinux.org/packages/chordpro-git

Environment:

  • OS: Manjaro Linux (Rolling)
  • Compositor: GNOME (Wayland) with 3 monitors attached
  • ChordPro Core: 6.090.1
  • wxWidgets: wxwidgets-gtk3 3.2.9-4
  • GTK: gtk3 1:3.24.51-1
  • Perl: v5.42.0 (x86_64-linux-thread-multi)

Console Output:

  1. Launch wxchordpro in a Wayland session.
  2. Attempt to open the preview window (or click the preview button).
  3. The application crashes instantly and exits with error code 1.
This is ChordPro core 6.090.1
Gdk-Message: 10:19:39.087: Error 71 (Protocol error) dispatching to Wayland display.

Technical Analysis (WAYLAND_DEBUG=1):

Running the application with WAYLAND_DEBUG=1 reveals that the crash is caused by an explicit sync mismatch. The toolkit requests explicit sync but subsequently attempts to attach a non-DMA buffer. Wayland strictly mandates that explicit sync (wp_linux_drm_syncobj) can only be used with dmabuf buffers.

Here are the relevant final lines from the Wayland debug log:

[2608524.731] {Default Queue}  -> wp_linux_drm_syncobj_manager_v1#53.get_surface(new id wp_linux_drm_syncobj_surface_v1#65, wl_surface#57)
...
[2608525.183] {EGLSurface(57/0x5649a1e98210)}  -> zwp_linux_dmabuf_v1#52.create_params(new id zwp_linux_buffer_params_v1#72)
...
[2608537.993] {Default Queue}  -> wl_surface#57.attach(wl_buffer#43, 0, 0) 
...
[2608538.572] {Display Queue} wl_display#1.error(wp_linux_drm_syncobj_surface_v1#65, 2, "Explicit Sync only supported on dmabuf buffers")

Note: wl_buffer#43 was established earlier in the log as a standard buffer, not the hardware-accelerated buffer the toolkit generated.

Workarounds:

This appears to be an upstream issue with how wxWebView / WebKitGTK handles hardware acceleration and explicit sync. I found two effective workarounds:

  1. Disable WebKit Compositing (Best Native Fix): Running the application with WEBKIT_DISABLE_COMPOSITING_MODE=1 wxchordpro completely resolves the crash. The internal preview window functions correctly under Wayland.

  2. Use External PDF Viewer: Adding the following to ~/.config/wxchordpro/wxchordpro opens the preview in a separate PDF viewer successfully (though View > Preview Panel will still crash the main app):

[preferences]
enable_pdfviewer=1

joelvaz0x01 commented on 2026-02-25 16:37 (UTC)

@SmileyChris I could not reproduce the issue you had, but the perl-Alien-wxWidgets library as been updated to v0.73, so there was probably some incompatibility with the last version of the wxwidgets-gtk3. Let me know if the issue persists.

SmileyChris commented on 2026-02-25 04:19 (UTC)

Trying to open the preview panel in wxchordpro (either via the view menu or the Preview button) results in a crash for me:

17:15:15: Debug: window wxMenuBar@0x55cceeb74fc0 ("menubar") lost focus even though it didn't have it Gdk-Message: 17:15:16.063: Error 71 (Protocol error) dispatching to Wayland display.