Hi Torquil,
On 06/10/13 13:53, Torquil Macdonald Sørensen wrote:
Package: ekiga
Version: 4.0.1-2+b2
Severity: important
While a call is ongoing, I'm having problems quitting Ekiga.
I'm calling the "echo test" address sip:[email protected]. The call starts,
and then I try the different ways of quitting described above.
While the call is ongoing, the following have no effect: "Call->Hangup" and
"Call->Close" menu items in the call window. Red "hangup" button in the call
window, and the x-button in the call window title bar.
I have sometimes this too, I will look into it.
Using the "Chat->Quit" main window menu item or the "Quit" systray item,
results in a segfault. The segfault is accompanied by the following gdb-output:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffa03d1700 (LWP 5165)]
0x00007ffff4395d5d in OpalPluginControl::Call(void*, unsigned int*, void*)
const () from /usr/lib/libopal.so.3.10.10
Could you give the gdb trace in this case? See
http://wiki.ekiga.org/index.php/Debugging_Ekiga#How_to_get_a_stack_backtrace_from_a_crash_or_freeze
for how to do that.
In addition, I have experienced another "event" while running ekiga through gdb,
which I think (but not positive) happened while trying to close the call window
or using the hangup button:
[New Thread 0x7fffa0412700 (LWP 4602)]
[Thread 0x7fffa3fff700 (LWP 4588) exited]
[Thread 0x7fffa0412700 (LWP 4602) exited]
[New Thread 0x7fffa03d1700 (LWP 4719)]
osutils.cxx(2294) PTLib Possible deadlock in read/write mutex
0x7fffb8006d20 :
thread-id=140736777512704 (0x7fffd5a16700), readers=0, writers=1
thread-id=140736777778944 (0x7fffd5a57700), readers=1, writers=0
osutils.cxx(2294) PTLib Possible deadlock in read/write mutex
0x7fffb4006ce0 :
thread-id=140735881746176 (0x7fffa03d1700), readers=1, writers=0
thread-id=140736777512704 (0x7fffd5a16700), readers=1, writers=1
thread-id=140737352582912 (0x7ffff7e84700), readers=1, writers=0
assert.cxx(112) PWLib Assertion fail: Function pthread_mutex_lock failed,
file ptlib/unix/tlibthrd.cxx, line 1552, Error=107
Assertion fail: Function pthread_mutex_lock failed, file
ptlib/unix/tlibthrd.cxx, line 1552, Error=107
<A>bort, <C>ore dump, <T>hrow exception, <I>gnore? [New Thread 0x7fffa0390700
(LWP 4723)]
[Thread 0x7fffa0390700 (LWP 4723) exited]
[New Thread 0x7fffa034f700 (LWP 4724)]
[Thread 0x7fffa034f700 (LWP 4724) exited]
[New Thread 0x7fffa030e700 (LWP 4725)]
[Thread 0x7fffa030e700 (LWP 4725) exited]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffd5a57700 (LWP 4581)]
0x00007ffff3e54f3a in PWaitAndSignal::PWaitAndSignal(PSync const&, bool) ()
from /usr/lib/libopal.so.3.10.10
Unfortunately, this appears from time to time, depending on slowness of
network/servers as far as I noticed. I will look into it also, but I
think it will be addressed only by a new major release.
I'm using pulseaudio and have selected pulseaudio in all Ekiga audio settings.
--
Eugen
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
