| 1 |
Hi, |
| 2 |
|
| 3 |
a weird problem happens, when I start qjackctl: |
| 4 |
|
| 5 |
No dialog of qjackctl is shown. |
| 6 |
|
| 7 |
The mouse cursor is still responding to mouse movements but |
| 8 |
"clicks" do not reach openbox anymore and therefore an |
| 9 |
interaction is no longer be possible. |
| 10 |
|
| 11 |
No audio setup is done. |
| 12 |
|
| 13 |
Only way out: Switch to the console (ALT-SHIFT 1) and |
| 14 |
kill the process of qjackctl. |
| 15 |
|
| 16 |
Dmesg shows nothing related. |
| 17 |
|
| 18 |
I have no clue, what's happening here, since the behaviour |
| 19 |
seems completly unrelated. |
| 20 |
|
| 21 |
Software versions: |
| 22 |
[I] media-sound/qjackctl |
| 23 |
Available versions: 0.4.5 {alsa dbus debug portaudio} |
| 24 |
Installed versions: 0.4.5(11:13:35 AM 02/17/2019)(alsa -dbus -debug -portaudio) |
| 25 |
Homepage: http://qjackctl.sourceforge.net/ |
| 26 |
Description: Qt GUI to control the JACK Audio Connection Kit and ALSA sequencer connections |
| 27 |
|
| 28 |
[I] media-sound/jack-audio-connection-kit |
| 29 |
Available versions: 0.125.0 {alsa altivec coreaudio debug doc examples oss pam ABI_MIPS="n32 n64 o32" ABI_PPC="32 64" ABI_S390="32 64" ABI_X86="32 64 x32" CPU_FLAGS_X86="3dnow sse"} |
| 30 |
Installed versions: 0.125.0(04:37:40 AM 01/14/2019)(alsa pam -altivec -coreaudio -debug -doc -examples -oss ABI_MIPS="-n32 -n64 -o32" ABI_PPC="-32 -64" ABI_S390="-32 -64" ABI_X86="64 -32 -x32" CPU_FLAGS_X86="3dnow sse") |
| 31 |
Homepage: http://www.jackaudio.org |
| 32 |
Description: A low-latency audio server |
| 33 |
|
| 34 |
[I] virtual/jack |
| 35 |
Available versions: 0 {ABI_MIPS="n32 n64 o32" ABI_PPC="32 64" ABI_S390="32 64" ABI_X86="32 64 x32"} |
| 36 |
Installed versions: 0(07:59:58 AM 09/16/2018)(ABI_MIPS="-n32 -n64 -o32" ABI_PPC="-32 -64" ABI_S390="-32 -64" ABI_X86="64 -32 -x32") |
| 37 |
Description: Virtual for JACK Audio Connection Kit |
| 38 |
|
| 39 |
|
| 40 |
For any help I thank you in advance! |
| 41 |
Cheers! |
| 42 |
Meino |
Archives