Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
pipewire
pipewire
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 234
    • Issues 234
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 4
    • Merge Requests 4
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • PipeWire
  • pipewirepipewire
  • Issues
  • #684

Closed
Open
Created Feb 06, 2021 by philip ross@pgbross

Ardour6.5 logs jack-client 0x562eb7a94340: not implemented

Version, Distribution, Desktop Environment:

PipeWire 0.3.21-2.fc33 (from copr nightly), Fedora 33, Gnome

Description of Problem: On starting Ardour6.5, journal shows jack-client 0x562eb7a94340: not implemented.

How Reproducible: Every time load session in Ardour6.5

Steps to Reproduce:

Using ardour6-backend-jack as the audio setup.

  1. Start Ardour 6.5
  2. Create new session or load existing session
  3. Review journalctl -e

Actual Results:

jack-client 0x562eb7a94340: not implemented

Mostly Ardour6.5 then runs normally, though is prone to crashing on altering the routing connections from within the routing grid for eg. the Master bus.

Expected Results:

No error.

Additional Info Eg. pw-dump > file (As Attachment Please):

Here is the full log of startup, also showing link-factory issues.

j.log

Of note but perhaps unrelated to the start-up issue, on save-and-quit the journal shows Ardour crashing in cycle_signal.

Feb 06 13:35:38 ab350n systemd-coredump[9291]: [LNK] Process 9103 (ArdourGUI) of user 1000 dumped core.
                                               
                                               Stack trace of thread 9282:
                                               #0  0x00007fdc1540b619 cycle_signal (libjack.so.0 + 0x15619)
                                               #1  0x00007fdc0401ab92 _ZN6ARDOUR16JACKAudioBackend14process_threadEv (libjack_audiobackend.so + 0x19b92)
                                               #2  0x00007fdc1866284b loop_iterate (libspa-support.so + 0x684b)
                                               #3  0x00007fdc14cc9427 do_loop (libpipewire-0.3.so.0 + 0x2b427)
                                               #4  0x00007fdc16f753f9 start_thread (libpthread.so.0 + 0x93f9)
                                               #5  0x00007fdc16599b53 __clone (libc.so.6 + 0x101b53)

ardour-crash-onclose.log

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None