I can only run pd when configured with Jack support, if I switch the non real time option ./pd -nrt
otherwhise it ./pd Segmentation fault
pd-0.48-0test2/bin/pd [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7ffff7f32700 (LWP 16148)] [New Thread 0x7ffff7eb1700 (LWP 16150)]
Thread 3 "pd" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7ffff7eb1700 (LWP 16150)] 0x00007ffff78b8f96 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0
(IOhannes: that's on Linux)
Just tried to compile pd-0.47-1 with jack for reference:
./pd disabling real-time priority due to missing pd-watchdog (/pd-0.47-1/src/bin/pd-watchdog) Error in startup script: couldn't read file "/pd-0.47-1/src/tcl//pd-gui.tcl": no such file or directory
maybe something on my system got broken with the Mint 18.2 update?
On 2017년 07월 19일 21:25, Max wrote:
I can only run pd when configured with Jack support, if I switch the non real time option ./pd -nrt
otherwhise it ./pd Segmentation fault
pd-0.48-0test2/bin/pd [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7ffff7f32700 (LWP 16148)] [New Thread 0x7ffff7eb1700 (LWP 16150)]
Thread 3 "pd" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7ffff7eb1700 (LWP 16150)] 0x00007ffff78b8f96 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0
(IOhannes: that's on Linux)
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
On 07/19/2017 10:12 PM, Max wrote:
Just tried to compile pd-0.47-1 with jack for reference:
./pd
what's your cwd?
disabling real-time priority due to missing pd-watchdog (/pd-0.47-1/src/bin/pd-watchdog) Error in startup script: couldn't read file "/pd-0.47-1/src/tcl//pd-gui.tcl": no such file or directory
at least this helped me find a regression, where Pd would die if started with -rt but pd-watchdog cannot be found. this is most likely your problem (the other question is, *why* Pd cannot find pd-watchdog and pd-gui on your system)
mds IOhannes
On 2017년 07월 19일 22:23, IOhannes m zmölnig wrote:
On 07/19/2017 10:12 PM, Max wrote:
Just tried to compile pd-0.47-1 with jack for reference:
./pd
what's your cwd?
~/somepath/pd-0.47-1/src/bin/
disabling real-time priority due to missing pd-watchdog (~/somepath/pd-0.47-1/src/bin/pd-watchdog) Error in startup script: couldn't read file "~/somepath/pd-0.47-1/src/tcl//pd-gui.tcl": no such file or directory
at least this helped me find a regression, where Pd would die if started with -rt but pd-watchdog cannot be found. this is most likely your problem (the other question is, *why* Pd cannot find pd-watchdog and pd-gui on your system)
Cool. Anything I can do to narrow this down?
On 2017년 07월 19일 21:25, Max wrote:
./pd Segmentation fault
if I do this, there is an output in the jack logs. It looks like this:
Wed Jul 19 23:27:15 2017: ERROR: Cannot read socket fd = 25 err = Broken pipe Wed Jul 19 23:27:15 2017: ERROR: Could not read notification result Wed Jul 19 23:27:15 2017: ERROR: ClientNotify fails name = system notification = 0 val1 = 0 val2 = 0 Wed Jul 19 23:27:15 2017: ERROR: NotifyAddClient new_client fails name = pure_data Wed Jul 19 23:27:15 2017: ERROR: Cannot notify add client Wed Jul 19 23:27:15 2017: ERROR: Cannot create new client Wed Jul 19 23:27:15 2017: ERROR: Cannot write socket fd = 23 err = Broken pipe Wed Jul 19 23:27:15 2017: ERROR: CheckRes error Wed Jul 19 23:27:15 2017: ERROR: JackRequest::ClientOpen write error name = pure_data
what is this?
On 2017-07-19 21:25, Max wrote:
I can only run pd when configured with Jack support, if I switch the non real time option ./pd -nrt
otherwhise it ./pd Segmentation fault
ok. i think i found the culprit and fixed it in in the "more feedback fixes" branch [116]. actually this fixes the "pd -nrt crashes if it cannot find pd-watchdog", which might be the cause of your problem - or not.
so could you test this branch and see whether the crash goes away?
fgasmdr IOhannes
[116] https://github.com/pure-data/pure-data/pull/116
PS: incidentally, this branch also contains a few updates of your German translation. i hope you like it.
On 2017년 07월 20일 10:20, IOhannes m zmoelnig wrote:
On 2017-07-19 21:25, Max wrote:
I can only run pd when configured with Jack support, if I switch the non real time option ./pd -nrt
otherwhise it ./pd Segmentation fault
ok. i think i found the culprit and fixed it in in the "more feedback fixes" branch [116]. actually this fixes the "pd -nrt crashes if it cannot find pd-watchdog", which might be the cause of your problem - or not.
so could you test this branch and see whether the crash goes away?
Thanks IOhannes, unfortunately it did not change.
pure-data-update-feedback-fixes/bin$ ./pd Segmentation fault
here are two lines from the system log:
kernel: [72257.667642] pd[22824]: segfault at 4 ip 00007f3e54d87f96 sp 00007f3e55383ae0 error 4 in libjack.so.0.1.0[7f3e54d51000+51000] kernel: [72561.641849] pd[9626]: segfault at 4 ip 00007fddd854df96 sp 00007fddd8b49ae0 error 4 in libjack.so.0.1.0[7fddd8517000+51000]
PS: incidentally, this branch also contains a few updates of your German translation. i hope you like it.
Oh, something I did lightyears ago for matjus desire data and then got pulled into Pd-extended now arrived in vanilla? I'm thrilled, probably need to switch my system language to German to test this :)
It stayed the same with test3. Is anyone else running it fine with Jack on Linux? I'd like to compare the setup (jack versions??) to help narrow it down.
On 07/20/2017 10:09 PM, Max wrote:
It stayed the same with test3. Is anyone else running it fine with Jack on Linux? I'd like to compare the setup (jack versions??) to help narrow it down.
yes, i'm running Pd with jack without a problem (Debian/sid)
gfmadsr IOhannes
On 07/20/2017 10:19 PM, IOhannes m zmölnig wrote:
On 07/20/2017 10:09 PM, Max wrote:
It stayed the same with test3. Is anyone else running it fine with Jack on Linux? I'd like to compare the setup (jack versions??) to help narrow it down.
yes, i'm running Pd with jack without a problem (Debian/sid)
jackd2: 1.9.10+20150825git1ed50c92~dfsg-5
so i think we *do* need a backtrace. compile Pd with "--enable-debug", then:
$ gdb ./pd
(gdb) run
[...]
(gdb) bt
(in your last attempt you forgot the crucial last command "bt", which will print out the actual backtrace)
don't get confused by the "watchdog: signaling pd..." messages (i suggested to use "-nrt" to get rid of those messages; but since the problem can only be seen with "-rt", you have to get through that...or remove the offending line src/s_watchdog.c:49 before recompilation...)
you might also want to read [1] to produce an even better backtrace.
gfmsard IOhannes
On 2017년 07월 20일 22:27, IOhannes m zmölnig wrote:
On 07/20/2017 10:19 PM, IOhannes m zmölnig wrote:
$ gdb ./pd (gdb) run [...] (gdb) bt
run Starting program: /path/pd-0.48-0test3/bin/pd [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7ffff7f32700 (LWP 21697)] [New Thread 0x7ffff7eb1700 (LWP 21699)]
Thread 3 "pd" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7ffff7eb1700 (LWP 21699)] 0x00007ffff78b8f96 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 (gdb) bt #0 0x00007ffff78b8f96 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 #1 0x00007ffff78b99c5 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 #2 0x00007ffff7893fc8 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 #3 0x00007ffff78bbb6a in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 #4 0x00007ffff78b6aa0 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 #5 0x00007ffff766c6ba in start_thread (arg=0x7ffff7eb1700) at pthread_create.c:333 #6 0x00007ffff6e953dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109
is that helpful or should I try one of these options?
On 07/20/2017 10:40 PM, Max wrote:
Thread 3 "pd" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7ffff7eb1700 (LWP 21699)] 0x00007ffff78b8f96 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 (gdb) bt #0 0x00007ffff78b8f96 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 #1 0x00007ffff78b99c5 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 #2 0x00007ffff7893fc8 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 #3 0x00007ffff78bbb6a in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 #4 0x00007ffff78b6aa0 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 #5 0x00007ffff766c6ba in start_thread (arg=0x7ffff7eb1700) at pthread_create.c:333 #6 0x00007ffff6e953dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109
is that helpful or should I try one of these options?
no, it's not helpful :-( please install the debug package(s) for libjack, and read the section about backtraces for multithreaded programs.
gamrds IOhannes
On 2017년 07월 21일 07:43, IOhannes m zmölnig wrote:
On 07/20/2017 10:40 PM, Max wrote:
Thread 3 "pd" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7ffff7eb1700 (LWP 21699)] 0x00007ffff78b8f96 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 (gdb) bt #0 0x00007ffff78b8f96 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 #1 0x00007ffff78b99c5 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 #2 0x00007ffff7893fc8 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 #3 0x00007ffff78bbb6a in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 #4 0x00007ffff78b6aa0 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 #5 0x00007ffff766c6ba in start_thread (arg=0x7ffff7eb1700) at pthread_create.c:333 #6 0x00007ffff6e953dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109
is that helpful or should I try one of these options?
no, it's not helpful :-( please install the debug package(s) for libjack, and read the section about backtraces for multithreaded programs.
I see.
(gdb) run Starting program: /path/pd-0.48-0test3/bin/pd [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7ffff7f32700 (LWP 27779)] [New Thread 0x7ffff7eb1700 (LWP 27781)]
Thread 3 "pd" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7ffff7eb1700 (LWP 27781)] 0x00007ffff78b8f96 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0
(gdb) thread apply all bt Thread 3 (Thread 0x7ffff7eb1700 (LWP 27781)): #0 0x00007ffff78b8f96 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 #1 0x00007ffff78b99c5 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 #2 0x00007ffff7893fc8 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 #3 0x00007ffff78bbb6a in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 #4 0x00007ffff78b6aa0 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 #5 0x00007ffff766c6ba in start_thread (arg=0x7ffff7eb1700) at pthread_create.c:333 #6 0x00007ffff6e953dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109
Thread 2 (Thread 0x7ffff7f32700 (LWP 27779)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007ffff78b78cc in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 #2 0x00007ffff78aa828 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 #3 0x00007ffff78b6aa0 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 #4 0x00007ffff766c6ba in start_thread (arg=0x7ffff7f32700) at pthread_create.c:333 #5 0x00007ffff6e953dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109
better?
On 07/21/2017 11:28 AM, Max wrote:
On 2017년 07월 21일 07:43, IOhannes m zmölnig wrote:
On 07/20/2017 10:40 PM, Max wrote:
Thread 3 "pd" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7ffff7eb1700 (LWP 21699)] 0x00007ffff78b8f96 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 (gdb) bt #0 0x00007ffff78b8f96 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 #1 0x00007ffff78b99c5 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 #2 0x00007ffff7893fc8 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 #3 0x00007ffff78bbb6a in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 #4 0x00007ffff78b6aa0 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 #5 0x00007ffff766c6ba in start_thread (arg=0x7ffff7eb1700) at pthread_create.c:333 #6 0x00007ffff6e953dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109
is that helpful or should I try one of these options?
no, it's not helpful :-( please install the debug package(s) for libjack, and read the section about backtraces for multithreaded programs.
I see.
(gdb) run Starting program: /path/pd-0.48-0test3/bin/pd [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7ffff7f32700 (LWP 27779)] [New Thread 0x7ffff7eb1700 (LWP 27781)]
Thread 3 "pd" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7ffff7eb1700 (LWP 27781)] 0x00007ffff78b8f96 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0
(gdb) thread apply all bt Thread 3 (Thread 0x7ffff7eb1700 (LWP 27781)): #0 0x00007ffff78b8f96 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 #1 0x00007ffff78b99c5 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 #2 0x00007ffff7893fc8 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 #3 0x00007ffff78bbb6a in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 #4 0x00007ffff78b6aa0 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 #5 0x00007ffff766c6ba in start_thread (arg=0x7ffff7eb1700) at pthread_create.c:333 #6 0x00007ffff6e953dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109
Thread 2 (Thread 0x7ffff7f32700 (LWP 27779)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007ffff78b78cc in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 #2 0x00007ffff78aa828 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 #3 0x00007ffff78b6aa0 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 #4 0x00007ffff766c6ba in start_thread (arg=0x7ffff7f32700) at pthread_create.c:333 #5 0x00007ffff6e953dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109
better?
somewhat, but not much.
#1 0x00007ffff78b78cc in ?? () from
/usr/lib/x86_64-linux-gnu/libjack.so.0
this basically tells us, that it is crashing somewhere in libjack, but the actual place/function in which this is happening is unknown ("??").
i think, you are still missing the debug packages of libjack. you need to enable to debugsym repository [1], and then install the "libjack-jackd2-0-dbgsym" package (if libjack-jackd2-0 provides your the libjack.so). to you are unsure about the libjack.so provider, install the package printed out by this:
dpkg -S /usr/lib/x86_64-linux-gnu/libjack.so.0 | sed -e 's|:.*|-dbgsym|'
fgmdsr IOhannes
On 07/21/2017 12:51 PM, IOhannes m zmölnig wrote:
better?
somewhat, but not much.
apart from that:
(Operation not permitted)" error (on the console) that i get?
different backend: './pd -verbose -rt -alsa'
gfmards IOhannes
On 2017년 07월 21일 13:12, IOhannes m zmölnig wrote:
On 07/21/2017 12:51 PM, IOhannes m zmölnig wrote:
better?
somewhat, but not much.
apart from that:
- what's the output of 'ulimit -a'
- is there a difference if you start jackd with/without realtime settings?
- is there a difference if you start jackd with/without memory locking?
- does it crash if you start Pd without jackd running?
- why don't you get the "Cannot lock down XXX byte memory area
(Operation not permitted)" error (on the console) that i get?
- what's the output of Pd (on the terminal and/or console) if you use a
different backend: './pd -verbose -rt -alsa'
IOhannes, thanks for your patience.
dpkg -S /usr/lib/x86_64-linux-gnu/libjack.so.0 | sed -e 's|:.*|-dbgsym|'
gives
libjack-jackd2-0-dbgsym
Following https://wiki.ubuntu.com/Debug%20Symbol%20Packages the variable $(lsb_release -cs) gives me "sonya" on Mint 18.2, had to change this manually to xenial..... Thinking of not installing Mint the next time or going for something like LMDE, debian or arch... anyway, that's OT. However, I have the KXStudio repositories installed, so the standard Ubuntu debug symbols don't help me, because they are for a different version. I should try downgrading jack, maybe that already solves the issue.
ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 30618 max locked memory (kbytes, -l) unlimited max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 95 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 30618 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited
no, still segfaults
different backend: './pd -verbose -rt -alsa'
/pd-0.48-0test3/bin$ ./pd -verbose -rt -alsa sys_audioapi set to 1 input channels = 2, output channels = 2 Pd-0.48.0 ("test3") compiled 22:35:07 Jul 20 2017 port 5401 TCL_LIBRARY="../lib/tcl/library" TK_LIBRARY="../lib/tk/library" wish "../tcl//pd-gui.tcl" 5401 Waiting for connection request... ... connected ../bin/pd-watchdog open: /etc/pd/gem.conf: No such file or directory open: /home/max/.pd/gem.conf: No such file or directory open: ./gem.conf: No such file or directory
Then switching to jack output in Pd for the fun:
Segmentation fault
And in the jack log: Fri Jul 21 13:27:43 2017: ERROR: Cannot read socket fd = 28 err = Broken pipe Fri Jul 21 13:27:43 2017: ERROR: Could not read notification result Fri Jul 21 13:27:43 2017: ERROR: ClientNotify fails name = system notification = 0 val1 = 0 val2 = 0 Fri Jul 21 13:27:43 2017: ERROR: NotifyAddClient new_client fails name = pure_data Fri Jul 21 13:27:43 2017: ERROR: Cannot notify add client Fri Jul 21 13:27:43 2017: ERROR: Cannot create new client Fri Jul 21 13:27:43 2017: ERROR: Cannot write socket fd = 26 err = Broken pipe Fri Jul 21 13:27:43 2017: ERROR: CheckRes error Fri Jul 21 13:27:43 2017: ERROR: JackRequest::ClientOpen write error name = pure_data
no:
./pd 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 open: /etc/pd/gem.conf: No such file or directory open: /home/max/.pd/gem.conf: No such file or directory open: ./gem.conf: No such file or directory
how?
On Fre, 2017-07-21 at 13:12 +0200, IOhannes m zmölnig wrote:
- why don't you get the "Cannot lock down XXX byte memory area
(Operation not permitted)" error (on the console) that i get?
I get that, too:
$ pd -jack -channels 2 -rt Cannot lock down 1186 byte memory area (Operation not permitted) Cannot lock down 82274202 byte memory area (Operation not permitted) Cannot lock down 422 byte memory area (Operation not permitted)
And was wondering: Why does it appear suddenly with recent versions of Pd?
Roman
On 2017년 07월 21일 12:51, IOhannes m zmölnig wrote:
On 07/21/2017 11:28 AM, Max wrote:
On 2017년 07월 21일 07:43, IOhannes m zmölnig wrote:
i think, you are still missing the debug packages of libjack. you need to enable to debugsym repository [1], and then install the "libjack-jackd2-0-dbgsym" package (if libjack-jackd2-0 provides your the libjack.so).
I think that KXStudio doesn't provide the debug symbol version, so I need to downgrade libjackd2-0 to 1.9.10+20150825git1ed50c92~dfsg-1ubuntu1 from 2:1.9.11~20161209-1~xenial5. However, that forces me to remove 20 depending packages, what I just went ahead with...
i have no more audio now... weep.
I want to go back. Package management seems like an awesome idea until this. Just give me a download including all the libraries statically linked and I will happily download a few MB more.... /rant end./
On 07/21/2017 04:49 PM, Max wrote:
On 2017년 07월 21일 12:51, IOhannes m zmölnig wrote:
On 07/21/2017 11:28 AM, Max wrote:
On 2017년 07월 21일 07:43, IOhannes m zmölnig wrote:
i think, you are still missing the debug packages of libjack. you need to enable to debugsym repository [1], and then install the "libjack-jackd2-0-dbgsym" package (if libjack-jackd2-0 provides your the libjack.so).
I think that KXStudio doesn't provide the debug symbol version, so I need to downgrade libjackd2-0 to 1.9.10+20150825git1ed50c92~dfsg-1ubuntu1 from 2:1.9.11~20161209-1~xenial5. However, that forces me to remove 20 depending packages, what I just went ahead with...
i have no more audio now... weep.
more important: did the crash go away with the downgrade?
I want to go back. Package management seems like an awesome idea until this. Just give me a download including all the libraries statically linked and I will happily download a few MB more....
this won't help you at all in the given situation, where you have multiple applications (like Pd) talking to a single server (like jackd). they *must* share some common infrastructure.
mgfdst IOhannes
On 2017년 07월 21일 20:49, IOhannes m zmölnig wrote:
On 07/21/2017 04:49 PM, Max wrote:
i have no more audio now... weep.
more important: did the crash go away with the downgrade?
I ended up with a broken Jack so I could not test this.
I want to go back. Package management seems like an awesome idea until this. Just give me a download including all the libraries statically linked and I will happily download a few MB more....
this won't help you at all in the given situation, where you have multiple applications (like Pd) talking to a single server (like jackd). they *must* share some common infrastructure.
OK, still allow me to vent my frustration for a moment: For OS X and Windows you get precompiled binaries, while Linux users are expected to be almost fully qualified developers just for running an application. I mean sure, I can go back to Pd from the repositories (thanks IOhannes for the packaging work by the way, we love you). If you are not running debian testing but some Ubuntu (-derivate) that's version 0.46.7 of Pd. The latest and greatest.
We've talked about this at the convention for a moment, with Liam and me describing this Linux user perspective. Remember?
Dan also put in a lot of work into the install.txt to make it easier to follow for non-devs. Thanks Dan, we love you too.
(For Ubuntu users,) the next step would be to have a .deb file to install, or alternatively a PPA from which I can install a stable, testing and daily branch of Pd.
Someone said that setting up a PPA is trivial, so I am eager to try this. Actually I was already reading up on it, that's why I tried to compile the test version in the first place.
On 07/21/2017 09:33 PM, Max wrote:
OK, still allow me to vent my frustration for a moment: For OS X and Windows you get precompiled binaries, while Linux users are expected to be almost fully qualified developers just for running an application.
while i understand your frustration about having a broken system, i think you are barking up the wrong tree here.
your trouble is not, because you "just want to run the application". you managed to compile the application fine, without having to be a fully qualified developer.
the problem we are facing, however, is that you are experiencing a crash (which nobody else so far has been able to reproduce yet), and we want to debug that crash. debugging is more related to "fully qualified programming" than to "just running an application". all the serious trouble you've seen so far, is because we want to debug the problem; and your machine is so far the only one where the problem shows itself; that's why we depend on you.
if your system was an OSX machine (say, a Macbook Air) then you had two possibilities: either rely on "just running the application" and live with your problem, or to "be almost a fully qualified developer" and help finding the cause of the problem. the very same holds true for w32.
to quote dan:
This have never been an issue with OS X in the past so I *do not* think there is suddenly a major problem based on feedback from running Pd on *one machine*.
does this make you feel any better? (the problem *I* am facing right now, is that my support for digging this problem will have to end tonight, since more pressing things are on my agenda; which I regret very much for your sake, but about which I cannot do much...).
gfmrdsa IOhannes
On 2017년 07월 20일 22:27, IOhannes m zmölnig wrote:
On 07/20/2017 10:19 PM, IOhannes m zmölnig wrote:
On 07/20/2017 10:09 PM, Max wrote:
It stayed the same with test3. Is anyone else running it fine with Jack on Linux? I'd like to compare the setup (jack versions??) to help narrow it down.
yes, i'm running Pd with jack without a problem (Debian/sid)
jackd2: 1.9.10+20150825git1ed50c92~dfsg-5
KXStudio repos just pushed another version: 2:1.9.11+git20170722-1~xenial2 I recompiled Pd with a little hope that it would magically work now, unfortunately it's still segfaulting.
On 2017년 07월 20일 22:19, IOhannes m zmölnig wrote:
On 07/20/2017 10:09 PM, Max wrote:
It stayed the same with test3. Is anyone else running it fine with Jack on Linux? I'd like to compare the setup (jack versions??) to help narrow it down.
yes, i'm running Pd with jack without a problem (Debian/sid)
Jack2?
libjack-jackd2-0 2:1.9.11~20161209-1~xenial5 is what I am running.
I made sure that sampling rate and blocksize were set to the same values (albeit that did not even matter before) and it doesn't change anything now either.
Can I do anything else to pinpoint the problem?
On Don, 2017-07-20 at 22:30 +0200, Max wrote:
On 2017년 07월 20일 22:19, IOhannes m zmölnig wrote:
On 07/20/2017 10:09 PM, Max wrote:
It stayed the same with test3. Is anyone else running it fine with Jack on Linux? I'd like to compare the setup (jack versions??) to help narrow it down.
yes, i'm running Pd with jack without a problem (Debian/sid)
Jack2?
libjack-jackd2-0 2:1.9.11~20161209-1~xenial5 is what I am running.
I have:
libjack-jackd2-0 1.9.10+20150825git1ed50c92~dfsg-1ubuntu1
This is on Ubuntu 16.04.
Last time I had Pd segfault (it segfaulted only wit -jack), the list of linked libraries helped troubleshooting the issue:
$ ldd ~/.local/bin/pd linux-vdso.so.1 => (0x00007ffd9c33a000) libasound.so.2 => /usr/lib/x86_64-linux-gnu/libasound.so.2 (0x00007fa015b57000) libjack.so.0 => /usr/lib/x86_64-linux-gnu/libjack.so.0 (0x00007fa01590e000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fa0156f0000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fa0154ec000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fa0151e3000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fa014e18000) librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007fa014c10000) /lib64/ld-linux-x86-64.so.2 (0x0000555ed511d000) libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007fa01488e000) libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007fa014677000)
Roman
On 2017년 07월 21일 11:35, Roman Haefeli wrote:
On Don, 2017-07-20 at 22:30 +0200, Max wrote:
On 2017년 07월 20일 22:19, IOhannes m zmölnig wrote:
libjack-jackd2-0 2:1.9.11~20161209-1~xenial5 is what I am running.
libjack-jackd2-0 1.9.10+20150825git1ed50c92~dfsg-1ubuntu1
This is on Ubuntu 16.04.
Last time I had Pd segfault (it segfaulted only wit -jack), the list of linked libraries helped troubleshooting the issue:
$ ldd ~/.local/bin/pd linux-vdso.so.1 => (0x00007ffd9c33a000) libasound.so.2 => /usr/lib/x86_64-linux-gnu/libasound.so.2 (0x00007fa015b57000) libjack.so.0 => /usr/lib/x86_64-linux-gnu/libjack.so.0 (0x00007fa01590e000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fa0156f0000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fa0154ec000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fa0151e3000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fa014e18000) librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007fa014c10000) /lib64/ld-linux-x86-64.so.2 (0x0000555ed511d000) libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007fa01488e000) libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007fa014677000)
sorry about my ignorance Roman, but could you explain _how_ it helped?
path/pd-0.48-0test3/bin$ ldd ./pd linux-vdso.so.1 => (0x00007ffd55d15000) libasound.so.2 => /usr/lib/x86_64-linux-gnu/libasound.so.2 (0x00007fa456d28000) libjack.so.0 => /usr/lib/x86_64-linux-gnu/libjack.so.0 (0x00007fa456ad3000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fa4568b5000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fa4566b1000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fa4563a8000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fa455fdd000) librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007fa455dd5000) /lib64/ld-linux-x86-64.so.2 (0x000055bdcba37000) libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3 (0x00007fa455b89000) libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007fa455806000) libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007fa4555f0000) libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 (0x00007fa45556a000) libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 (0x00007fa455348000) liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x00007fa455126000) libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 (0x00007fa454e44000) libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007fa454bd4000) libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 (0x00007fa4549c0000)
On 07/21/2017 12:16 PM, Max wrote:
sorry about my ignorance Roman, but could you explain _how_ it helped?
mostly because libjack.so wasn't there at all. there was some problem with underlinking/weak-symbols, which became (somewhat) apparent by looking at the output of ldd.
gasmdr IOhannes
On Fre, 2017-07-21 at 12:16 +0200, Max wrote:
On 2017년 07월 21일 11:35, Roman Haefeli wrote:
On Don, 2017-07-20 at 22:30 +0200, Max wrote:
On 2017년 07월 20일 22:19, IOhannes m zmölnig wrote:
libjack-jackd2-0 2:1.9.11~20161209-1~xenial5 is what I am running.
libjack-jackd2-0 1.9.10+20150825git1ed50c92~dfsg-1ubuntu1
This is on Ubuntu 16.04.
Last time I had Pd segfault (it segfaulted only wit -jack), the list of linked libraries helped troubleshooting the issue:
[...]
sorry about my ignorance Roman, but could you explain _how_ it helped?
[...]
Sorry for not being more clear. My Pd was not linked against jack, although it was compiled with Jack support. As soon as I used '-jack' or switched to 'Jack' through menu, it crashed. But your Pd _is_ linked to libjack, so this is not the culprit.
Roman
On 20/07/17 21:19, IOhannes m zmölnig wrote:
On 07/20/2017 10:09 PM, Max wrote:
It stayed the same with test3. Is anyone else running it fine with Jack on Linux? I'd like to compare the setup (jack versions??) to help narrow it down.
yes, i'm running Pd with jack without a problem (Debian/sid)
me too, pd-0.48 test 3 works fine with JACK on Debian Stretch i386 (Atom netbook, will test other architectures later this week).
$ apt-cache policy libjack-jackd2-0 libjack-jackd2-0: Installed: 1.9.10+20150825git1ed50c92~dfsg-5 Candidate: 1.9.10+20150825git1ed50c92~dfsg-5 Version table: *** 1.9.10+20150825git1ed50c92~dfsg-5 500 500 http://ftp.uk.debian.org/debian stretch/main i386 Packages 100 /var/lib/dpkg/status