Qsynth fails to connect to jack: zombified - calling shutdown handler

Bug #456363 reported by hanzomon4
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
qsynth (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: qsynth

This just started a few days ago... I start qjackctl then qsynth and get this error message in the qsynth message window:

"SSE2 detected
zombified - calling shutdown handler
fluidsynth: error: Help! Lost the connection to the JACK server
SSE2 detected
zombified - calling shutdown handler
fluidsynth: error: Help! Lost the connection to the JACK server"

and this in a popup

"Qsynth: Failed to create the audio driver (jack)
cannot continue without it"

Sometimes it works but then I get a massive amount of xruns that eventually cause everything to get kicked out of the jackd server.

I tried to run fluidsynth from the CLI, while qysynth was running, to get more info and I got this error message:

"lash_open_socket: could not connect to host 'localhost', service '14541'
lash_comm_connect_to_server: could not create server connection
SSE2 detected
Connected to JACK server with client name 'LASH_Server'
Opened ALSA sequencer with client ID 131
Listening for connections
Created project project-1 in directory /home/hanzomon4/audio-projects/project-1
Added client 0960ff78-33a3-491f-9dd9-7d37a46b01c3 of class fluidsynth to project project-1
cannot read response from jack server (No such file or directory)
fluidsynth: error: Jack server not running?
Failed to create the audio driver
Client 0960ff78-33a3-491f-9dd9-7d37a46b01c3 removed from project project-1
Project project-1 removed"

ProblemType: Bug
Architecture: amd64
Date: Tue Oct 20 09:33:10 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: qsynth 0.2.5-2.2
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-9.152-rt
SourcePackage: qsynth
Uname: Linux 2.6.31-9-rt x86_64

Revision history for this message
hanzomon4 (hanzomon4) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.