pacmixer seg fault

[jr0n]

Running pacmixer as an unprivileged user on Debian jessie causes a Segmentation fault upon execution. Running the debug build fails to produce a log. All tests using pacmixer_run_tests succeed. Running pacmixer as root produces a "Waiting for connection..." dialog.

[KenjiTakahashi]

Are you sure that PulseAudio server is running (e.g. can pavucontrol see it properly)?
It looks that it's trying to run PA server under the hood (which it might if it's not already running) and fails. For some reason...
Would be also nice to see a stack trace of the segfault. Could you please do this (let's hope curses will not clutter gdb output...):

1. Compile with debug enabled.
2. Run gdb pacmixer.
3. Type run.
4. It should crash, type bt and paste the output.

I will try to find some time tomorrow to set up Debian VM and check if I can reproduce this.

[jr0n]

Thanks for the reply. pavucontrol is working correctly. Here is the output you requested:

[New Thread 0x7fffe92f6700 (LWP 2676) Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffe92f6700 (LWP 2676)] 0x00007ffff781ded1 in ?? () from /usr/lib/libgnustep-base.so.1.22 (gdb) bt #0 0x00007ffff781ded1 in ?? () from /usr/lib/libgnustep-base.so.1.22 #1 0x0000000000403217 in callback_add_func (self_=0x767830, name=0x7fffe40079e4 "Built-in Audio Analog Stereo", type=SINK, idx=0, data=0x7fffe92f56f0) at src/middleware.m:43 #2 0x0000000000410da9 in _cb_sink.part.10 () #3 0x00007ffff69d97d4 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x00007ffff3df353e in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-5.0.so #5 0x00007ffff3df38bb in pa_pdispatch_run () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-5.0.so #6 0x00007ffff69ce612 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #7 0x00007ffff3df7845 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-5.0.so #8 0x00007ffff69e2414 in pa_mainloop_dispatch () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #9 0x00007ffff69e27ea in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #10 0x00007ffff69e2890 in pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #11 0x00007ffff69f0873 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #12 0x00007ffff3e07178 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-5.0.so #13 0x00007ffff50f1062 in start_thread (arg=0x7fffe92f6700) at pthread_create.c:312 #14 0x00007ffff66fabfd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

[KenjiTakahashi]

I have just set up a debian80 VM and I am able to reproduce the problem. Will look into it ASAP.

BTW: It is generally nice to enclose stack traces and such in a code tag, ``` at beginning and end, like this:

#1 some trace

It's easier to read and does not cause references to other issues :-).

[KenjiTakahashi]

Just pushed updated master with a fix. Tried it in VM and works fine now. Let me know if there are any problems.

[jr0n]

The new build works perfectly. Thanks!