Startup crash on Debian linux

K

keantoken

New Member
Thread Starter
Joined
May 31, 2018
Messages
62
I am using Debian Sid and I get this a few seconds after REW starts. It works normally until it crashes which happens after a set time no matter what I do.

Here is the terminal log:

$ /home/keantoken/REW/roomeqwizard
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
setHWParams: Rate does not match (req. 384000, got 192000)
[xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
java: ../../src/xcb_io.c:278: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
Aborted


This started happening after an update. If it is settings related is there a config file I can delete?
 
John Mulcahy

John Mulcahy

REW Author
Joined
Apr 3, 2017
Messages
7,344
It looks audio related, given the mention of Jack, @phofman might have an idea what is happening. You could try restricting the rates that are tested on startup as described here.
 
K

keantoken

New Member
Thread Starter
Joined
May 31, 2018
Messages
62
That doesn't help and the terminal output is exactly the same. I reduced the pulseaudio samplerate to 192KHz and 48KHz with the same result.
 
K

keantoken

New Member
Thread Starter
Joined
May 31, 2018
Messages
62
When using pulseaudio with verbose terminal output I get this sequence repeating while REW is still open, the number increases each time:

I: [pulseaudio] client.c: Created 152 "Native client (UNIX socket client)"
D: [pulseaudio] protocol-native.c: Protocol version: remote 35, local 35
I: [pulseaudio] protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
D: [pulseaudio] protocol-native.c: SHM possible: yes
D: [pulseaudio] protocol-native.c: Negotiated SHM: yes
D: [pulseaudio] protocol-native.c: Memfd possible: yes
D: [pulseaudio] protocol-native.c: Negotiated SHM type: shared memfd
D: [pulseaudio] memblock.c: Using shared memfd memory pool with 1024 slots of size 64.0 KiB each, total size is 64.0 MiB, maximum usable slot size is 65472
D: [pulseaudio] srbchannel.c: SHM block is 65472 bytes, ringbuffer capacity is 2 * 32712 bytes
D: [pulseaudio] protocol-native.c: Enabling srbchannel...
D: [pulseaudio] module-augment-properties.c: Looking for .desktop file for java
D: [pulseaudio] protocol-native.c: Client enabled srbchannel.
I: [pulseaudio] client.c: Freed 152 "ALSA plug-in [java]"
I: [pulseaudio] protocol-native.c: Connection died.
I: [pulseaudio] client.c: Created 153 "Native client (UNIX socket client)"
D: [pulseaudio] protocol-native.c: Protocol version: remote 35, local 35
I: [pulseaudio] protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
D: [pulseaudio] protocol-native.c: SHM possible: yes
D: [pulseaudio] protocol-native.c: Negotiated SHM: yes
D: [pulseaudio] protocol-native.c: Memfd possible: yes
D: [pulseaudio] protocol-native.c: Negotiated SHM type: shared memfd
D: [pulseaudio] memblock.c: Using shared memfd memory pool with 1024 slots of size 64.0 KiB each, total size is 64.0 MiB, maximum usable slot size is 65472
D: [pulseaudio] srbchannel.c: SHM block is 65472 bytes, ringbuffer capacity is 2 * 32712 bytes
D: [pulseaudio] protocol-native.c: Enabling srbchannel...
D: [pulseaudio] module-augment-properties.c: Looking for .desktop file for java
D: [pulseaudio] protocol-native.c: Client enabled srbchannel.
I: [pulseaudio] client.c: Freed 153 "ALSA plug-in [java]"
I: [pulseaudio] protocol-native.c: Connection died.
 
John Mulcahy

John Mulcahy

REW Author
Joined
Apr 3, 2017
Messages
7,344
You could try renaming the libcsjsound_aarch64.so and/or libcsjsound_amd64.so files to inhibit Pavel's sound provider to see if that helps.
 
K

keantoken

New Member
Thread Starter
Joined
May 31, 2018
Messages
62
I removed them both and the terminal output is shortened to this:

$ /home/keantoken/REW/roomeqwizard
[xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
java: ../../src/xcb_io.c:278: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
Aborted
 
P

phofman

Member
Joined
Jun 26, 2019
Messages
137
keantoken said:
I am using Debian Sid and I get this a few seconds after REW starts. It works normally until it crashes which happens after a set time no matter what I do.

Here is the terminal log:

$ /home/keantoken/REW/roomeqwizard
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Click to expand...

This is log by the jack alsa plugin, from the alsa PCM device "jack" defined on default alsa config, which is trying to connect to the jack server. It tries always at start. The log is harmless.
keantoken said:
setHWParams: Rate does not match (req. 384000, got 192000)
Click to expand...

This is log by csjsound alsa lib, most likely when enumerating available rates. Should be harmless too.
keantoken said:
[xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
java: ../../src/xcb_io.c:278: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
Aborted
Click to expand...
IIUC some thread in java process being an X11 GUI app died.
keantoken said:
This started happening after an update. If it is settings related is there a config file I can delete?
Click to expand...
Update of REW or of debian?
 
P

phofman

Member
Joined
Jun 26, 2019
Messages
137
keantoken said:
When using pulseaudio with verbose terminal output I get this sequence repeating while REW is still open, the number increases each time:

I: [pulseaudio] client.c: Created 152 "Native client (UNIX socket client)"
D: [pulseaudio] protocol-native.c: Protocol version: remote 35, local 35
I: [pulseaudio] protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
D: [pulseaudio] protocol-native.c: SHM possible: yes
D: [pulseaudio] protocol-native.c: Negotiated SHM: yes
D: [pulseaudio] protocol-native.c: Memfd possible: yes
D: [pulseaudio] protocol-native.c: Negotiated SHM type: shared memfd
D: [pulseaudio] memblock.c: Using shared memfd memory pool with 1024 slots of size 64.0 KiB each, total size is 64.0 MiB, maximum usable slot size is 65472
D: [pulseaudio] srbchannel.c: SHM block is 65472 bytes, ringbuffer capacity is 2 * 32712 bytes
D: [pulseaudio] protocol-native.c: Enabling srbchannel...
D: [pulseaudio] module-augment-properties.c: Looking for .desktop file for java
D: [pulseaudio] protocol-native.c: Client enabled srbchannel.
I: [pulseaudio] client.c: Freed 152 "ALSA plug-in [java]"
I: [pulseaudio] protocol-native.c: Connection died.
I: [pulseaudio] client.c: Created 153 "Native client (UNIX socket client)"
D: [pulseaudio] protocol-native.c: Protocol version: remote 35, local 35
I: [pulseaudio] protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
D: [pulseaudio] protocol-native.c: SHM possible: yes
D: [pulseaudio] protocol-native.c: Negotiated SHM: yes
D: [pulseaudio] protocol-native.c: Memfd possible: yes
D: [pulseaudio] protocol-native.c: Negotiated SHM type: shared memfd
D: [pulseaudio] memblock.c: Using shared memfd memory pool with 1024 slots of size 64.0 KiB each, total size is 64.0 MiB, maximum usable slot size is 65472
D: [pulseaudio] srbchannel.c: SHM block is 65472 bytes, ringbuffer capacity is 2 * 32712 bytes
D: [pulseaudio] protocol-native.c: Enabling srbchannel...
D: [pulseaudio] module-augment-properties.c: Looking for .desktop file for java
D: [pulseaudio] protocol-native.c: Client enabled srbchannel.
I: [pulseaudio] client.c: Freed 153 "ALSA plug-in [java]"
I: [pulseaudio] protocol-native.c: Connection died.
Click to expand...

The log shows that the java pulse plugin connects to PA and later on disconnects. The pulse alsa plugin is configured as "default" java PCM device on standard linux distributions, again opened by the csjsound when enumerating PCM devices. IMO no problem here.
 
P

phofman

Member
Joined
Jun 26, 2019
Messages
137
keantoken said:
I removed them both and the terminal output is shortened to this:

$ /home/keantoken/REW/roomeqwizard
[xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
java: ../../src/xcb_io.c:278: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
Aborted
Click to expand...
IMO some thread in your java is dying and the X11 library does not like it. The question is why...
 
John Mulcahy

John Mulcahy

REW Author
Joined
Apr 3, 2017
Messages
7,344
If the problem happens a few seconds after the REW main window appears it may coincide with REW showing a dialog that displays progress enumerating audio mixers. Googling those xcb errors turns up some instances relating to SWT and GTK, but REW is a Swing application and Swing uses a single thread (the Event Dispatch Thread or EDT) for all GUI activity. I regularly run a customised repaint manager that checks for any violations of the EDT (i.e. painting activity off the EDT) and it is passing without errors, so difficult to see how that xcb error could arise.
 
K

keantoken

New Member
Thread Starter
Joined
May 31, 2018
Messages
62
It gives me an error about Jaxb, but while I am looking at the popup window it crashes with the same error:

$ /usr/lib/jvm/java-17-openjdk-amd64/bin/java -splash:/home/keantoken/REW/.install4j/s_1uqrgys.png -XX:+UseZGC -Xms128m -Xmx8192m -Dsun.java2d.opengl=True -classpath /home/keantoken/REW/.install4j/i4jruntime.jar:/home/keantoken/REW/.install4j/launcherd9d2fef3.jar:/home/keantoken/REW/./* install4j.roomeqwizard.RoomEQ_Wizard
[xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
java: ../../src/xcb_io.c:278: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
Aborted
 
P

phofman

Member
Joined
Jun 26, 2019
Messages
137
keantoken said:
It gives me an error about Jaxb,
Click to expand...
Interesting, with the two extra jars in the REW directory?

keantoken said:
but while I am looking at the popup window it crashes with the same error:

$ /usr/lib/jvm/java-17-openjdk-amd64/bin/java -splash:/home/keantoken/REW/.install4j/s_1uqrgys.png -XX:+UseZGC -Xms128m -Xmx8192m -Dsun.java2d.opengl=True -classpath /home/keantoken/REW/.install4j/i4jruntime.jar:/home/keantoken/REW/.install4j/launcherd9d2fef3.jar:/home/keantoken/REW/./* install4j.roomeqwizard.RoomEQ_Wizard
[xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
java: ../../src/xcb_io.c:278: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
Aborted
Click to expand...

That does look like some incompatibility of the java libs used by REW with the latest changes in debian libs.
 
K

keantoken

New Member
Thread Starter
Joined
May 31, 2018
Messages
62
Her is the jaxb error:

java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException occurred during startup

See Details for more information, please send it
to feedback@roomeqwizard.com


Debug info:


REW V5.20.14 running Debian JRE 17.0.5 64-bit on linux 6.1.0-5.2-liquorix-amd64 Locale: language en, keyboard US, UTF-8 at 96 DPI


Message:
java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException
Stack Trace:
javax/xml/bind/JAXBException
roomeqwizard.BB. (y:3338)
roomeqwizard.RoomEQ_Wizard.k(y:4604)
roomeqwizard.RoomEQ_Wizard.main(y:2631)
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
java.base/java.lang.reflect.Method.invoke(Method.java:568)
com.exe4j.runtime.LauncherEngine.launch(LauncherEngine.java:84)
com.install4j.runtime.launcher.UnixLauncher.start(UnixLauncher.java:69)
install4j.roomeqwizard.RoomEQ_Wizard.main(Unknown Source)
javax.xml.bind.JAXBException
java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641)
java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)
java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:520)
roomeqwizard.BB. (y:3338)
roomeqwizard.RoomEQ_Wizard.k(y:4604)
roomeqwizard.RoomEQ_Wizard.main(y:2631)
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
java.base/java.lang.reflect.Method.invoke(Method.java:568)
com.exe4j.runtime.LauncherEngine.launch(LauncherEngine.java:84)
com.install4j.runtime.launcher.UnixLauncher.start(UnixLauncher.java:69)
install4j.roomeqwizard.RoomEQ_Wizard.main(Unknown Source)


I wonder if this is even related to the XCB error or if it is just another error caused by trying to use Java 17.
 
John Mulcahy

John Mulcahy

REW Author
Joined
Apr 3, 2017
Messages
7,344
That error would usually mean the JAXB jars are not present, they need to be added separately since they are not part of Java 17.
 
K

keantoken

New Member
Thread Starter
Joined
May 31, 2018
Messages
62
I have jaxb installed. I only get this error if I try to run REW with Java 17.
 
John Mulcahy

John Mulcahy

REW Author
Joined
Apr 3, 2017
Messages
7,344
I'm not sure what you mean by installed. If the jars are not on the path when REW tries to run the classes will not be found. Java 8 includes JAXB so there's no need for them in that case.
 
K

keantoken

New Member
Thread Starter
Joined
May 31, 2018
Messages
62
Well it still crashes with the XCB error even while the JAXB error window is up, so I don't think JAXB is the issue.
 
You must log in or register to reply here.

Popular tags

20th century fox 4k blu-ray 4k uhd 4k ultrahd action adventure animated animation anime bass blu-ray calibration classic comedy comics denon dirac live disney dolby atmos drama fantasy hdmi 2.1 horror kaleidescape klipsch lionsgate marantz onkyo paramount pioneer rew romance sci-fi scream factory shout factory sony stormaudio subwoofer superhero svs terror thriller uhd ultrahd ultrahd 4k universal value electronics warner warner brothers well go usa
Top Bottom