Red Hat Bugzilla – Bug 373641
Last modified: 2012-08-06 10:54:57 EDT
Description of problem:
Twinkle crahes with SIGSEGV, after ending a call.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. call someone
2. press "end" button
3. twinkle crashes
crash of twinkle
twinkle ends the call without problem
Created attachment 253341 [details]
backtrace from gdb
Looks like a null dereference.
Odd. ok. I will take a look into it...
i386? I see your gdb is el5... but this is on f8, right?
Is there anything in your ~/.twinkle/twinkle.log that pertains to this?
Yes, it's i386. The gdb output is from el5, but the same behavior applies for f8
No, nothing in twinkle.log.
Looks like this might be something in the ccrtp libs.
What version of ccrtp do you have installed?
can you install the ccrtp debuginfo and re-run gdb?
Can you generate a twinkle.log with a failed session and attach it anyhow?
(Upstream asks for that on all bug reports).
I take it you are only seeing this in devel, not F8?
Can you try the twinkle from this scratch build (as soon as it's done)?
Houps, sorry for late answer. I need to reorganize my bugzilla mails I think.
My ccrtp version is ccrtp-1.5.1-1.
As the scratch build does not preserve the source rpm I can't try it. I'm using
this twinkle package under RHEL, recompiled from Fedora.
Created attachment 271191 [details]
backstrace from gdb with ccrtp-debuginfo
Created attachment 271211 [details]
Comparing straces and an educated guess shows that switching from ALSA to OSS
seems to fix the hang on clicking BYE. This might be heavily related to this
True, this solves the problem. I just found another user having same problem.
(In reply to comment #11)
> True, this solves the problem. I just found another user having same problem.
I'm not seeing this problem myself. What Headset are you using when calling with
twinkle? Is there any correlation? I'm on a Logitech headset with USB adapter.
no headset, using my build-in sound card in T60.
what about the others? Internal card as well?
Yes, however after I've reinstalled my computer I don't see this error. Andreas
can you please work with Igor Donev to get this resolved?
You no longer see the issue? Do we have someone who can duplicate it?
I still don't see it here at all...
Any further news here? Or should we just close this out?
(In reply to comment #17)
> Any further news here? Or should we just close this out?
Kevin, closing. Thank you for your time, this bug report itself has not been
very informative from my side. If I see the issue again I'll make sure to
troubleshoot it and get proper backtrace as well.