Created attachment 590424 [details]
File: backtrace

Created attachment 590425 [details]
File: maps

Created attachment 590426 [details]
File: dso_list

This happens all the time? Or was a one time thing? or ?

Every time that I attempt to run twinkle.  Appears to happen as well when attempting to recompile.  Trying to ensure it is the same error.

Just stumbled into the same mess when attempting to run linphone which leads me to believe this is probably something hardware/install-specific and not something specific to twinkle.  Will more than likely close this issue out.

Closing this one out.  Not really sure what happened on my system but I suspect some odd combination of updates being applied, prelink running, other packages installing.  Reinstalling Fedora resolved the issue.

I'm having a similar problem. It's a really poor solution having to reinstall my box to make this go away...

This is also happening on my system.  While I can accept this may not be a twinkle bug I would greatly appreciate some help figuring out where my config is incorrect.

Is the traceback exactly the same?

Can you attach your /etc/hosts file here?

$ cat ~/.cache/abrt/spool/ccpp-2012-08-08-11\:55\:28-17247/core_backtrace f69712fe393313f44607679e934bf5a67f39ec50 0x35925 raise libc.so.6 -
f69712fe393313f44607679e934bf5a67f39ec50 0x37251 abort libc.so.6 -
f69712fe393313f44607679e934bf5a67f39ec50 0x7564b __libc_message libc.so.6 -
f69712fe393313f44607679e934bf5a67f39ec50 0x1097c7 __fortify_fail libc.so.6 -
f69712fe393313f44607679e934bf5a67f39ec50 0x107980 __chk_fail libc.so.6 -
5f07707b5f8817b7e51c778be3b759ed702e18ff 0x28e73 - libccgnu2-1.8.so.0 -
5f07707b5f8817b7e51c778be3b759ed702e18ff 0x295f8 ost::IPV4Host::IPV4Host(char libccgnu2-1.8.so.0 -
bc2ff00f2a86e4baabce76d881d0f3961461871c 0x20091 - libcommoncpp.so.5 -
6088efab2ef3571c51fb041bb70b4ab626221ba4 0xee26 call_init.part.0 ld-linux-x86-64.so.2 -
6088efab2ef3571c51fb041bb70b4ab626221ba4 0xeee0 _dl_init_internal ld-linux-x86-64.so.2 -
6088efab2ef3571c51fb041bb70b4ab626221ba4 0x156a _dl_start_user ld-linux-x86-64.so.2 -
- 0x0 - - -
- 0x0 - - -
- 0x0 - - -

$ cat /etc/hosts
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6

abrt identified this bug as a duplicate of my crash but I still have the report in spool so I can attach the full backtrace if needed.

I have opted to quit twinkle and then start again in several seconds

apparently the initial session will never end (if you opt to quit)

I have tested in this way also
1. start computer (fedoara 17 )
2. start Twinkle 
3. after some minutes select "Quit'
I can see forever the PID of twinkle in my running programs
only reboot or kill -9 it will kill it


backtrace_rating: 3
Package: twinkle-1.4.2-17.fc17
OS Release: Fedora release 17 (Beefy Miracle)

Just run in.

backtrace_rating: 3
Package: twinkle-1.4.2-19.fc18
OS Release: Fedora release 18 (Spherical Cow)

install fedora 18 with twinkle selected, run twinkle

backtrace_rating: 3
Package: twinkle-1.4.2-19.fc18
OS Release: Fedora release 18 (Spherical Cow)

Just started twinkle and it failed with :

twinkle   
*** buffer overflow detected ***: twinkle terminated
======= Backtrace: ========= 
/lib64/libc.so.6(__fortify_fail+0x37)[0x3cae90a697]
/lib64/libc.so.6[0x3cae908810]
/lib64/libccgnu2-1.8.so.0[0x3cbc428e73]
/lib64/libccgnu2-1.8.so.0(_ZN3ost8IPV4HostC1EPKc+0xa8)[0x3cbc4295f8]
/lib64/libcommoncpp.so.5[0x3cbd4200f1]
/lib64/ld-linux-x86-64.so.2[0x3cae00ef36]
/lib64/ld-linux-x86-64.so.2[0x3cae00eff0]
/lib64/ld-linux-x86-64.so.2[0x3cae0015ca]
======= Memory map: ======== 
00400000-00714000 r-xp 00000000 fd:02 1857572                            /usr/bin/twinkle
00914000-00915000 r--p 00314000 fd:02 1857572                            /usr/bin/twinkle
00915000-0091a000 rw-p 00315000 fd:02 1857572                            /usr/bin/twinkle
00b19000-00b67000 rw-p 00319000 fd:02 1857572                            /usr/bin/twinkle
029b6000-029d7000 rw-p 00000000 00:00 0                                  [heap]
3cae000000-3cae020000 r-xp 00000000 fd:02 1836004                        /usr/lib64/ld-2.16.so
3cae220000-3cae221000 r--p 00020000 fd:02 1836004                        /usr/lib64/ld-2.16.so
3cae221000-3cae222000 rw-p 00021000 fd:02 1836004                        /usr/lib64/ld-2.16.so
3cae222000-3cae223000 rw-p 00000000 00:00 0
3cae400000-3cae415000 r-xp 00000000 fd:02 1838305                        /usr/lib64/libgcc_s-4.7.2-20121109.so.1
3cae415000-3cae614000 ---p 00015000 fd:02 1838305                        /usr/lib64/libgcc_s-4.7.2-20121109.so.1
3cae614000-3cae615000 r--p 00014000 fd:02 1838305                        /usr/lib64/libgcc_s-4.7.2-20121109.so.1
3cae615000-3cae616000 rw-p 00015000 fd:02 1838305                        /usr/lib64/libgcc_s-4.7.2-20121109.so.1
3cae800000-3cae9ad000 r-xp 00000000 fd:02 1836189                        /usr/lib64/libc-2.16.so
3cae9ad000-3caebad000 ---p 001ad000 fd:02 1836189                        /usr/lib64/libc-2.16.so
3caebad000-3caebb1000 r--p 001ad000 fd:02 1836189                        /usr/lib64/libc-2.16.so
3caebb1000-3caebb3000 rw-p 001b1000 fd:02 1836189                        /usr/lib64/libc-2.16.so
3caebb3000-3caebb8000 rw-p 00000000 00:00 0
3caec00000-3caec16000 r-xp 00000000 fd:02 1836708                        /usr/lib64/libpthread-2.16.so
3caec16000-3caee16000 ---p 00016000 fd:02 1836708                        /usr/lib64/libpthread-2.16.so
3caee16000-3caee17000 r--p 00016000 fd:02 1836708                        /usr/lib64/libpthread-2.16.so
3caee17000-3caee18000 rw-p 00017000 fd:02 1836708                        /usr/lib64/libpthread-2.16.so
3caee18000-3caee1c000 rw-p 00000000 00:00 0
3caf000000-3caf003000 r-xp 00000000 fd:02 1836696                        /usr/lib64/libdl-2.16.so
3caf003000-3caf202000 ---p 00003000 fd:02 1836696                        /usr/lib64/libdl-2.16.so
3caf202000-3caf203000 r--p 00002000 fd:02 1836696                        /usr/lib64/libdl-2.16.so
3caf203000-3caf204000 rw-p 00003000 fd:02 1836696                        /usr/lib64/libdl-2.16.so
3caf400000-3caf407000 r-xp 00000000 fd:02 1836711                        /usr/lib64/librt-2.16.so
3caf407000-3caf606000 ---p 00007000 fd:02 1836711                        /usr/lib64/librt-2.16.so
3caf606000-3caf607000 r--p 00006000 fd:02 1836711                        /usr/lib64/librt-2.16.so
3caf607000-3caf608000 rw-p 00007000 fd:02 1836711                        /usr/lib64/librt-2.16.so
3caf800000-3caf815000 r-xp 00000000 fd:02 1837519                        /usr/lib64/libz.so.1.2.7
3caf815000-3cafa14000 ---p 00015000 fd:02 1837519                        /usr/lib64/libz.so.1.2.7
3cafa14000-3cafa15000 r--p 00014000 fd:02 1837519                        /usr/lib64/libz.so.1.2.7
3cafa15000-3cafa16000 rw-p 00015000 fd:02 1837519                        /usr/lib64/libz.so.1.2.7
3cafc00000-3cafd00000 r-xp 00000000 fd:02 1836688                        /usr/lib64/libm-2.16.so
3cafd00000-3cafeff000 ---p 00100000 fd:02 1836688                        /usr/lib64/libm-2.16.so
3cafeff000-3caff00000 r--p 000ff000 fd:02 1836688                        /usr/lib64/libm-2.16.so
3caff00000-3caff01000 rw-p 00100000 fd:02 1836688                        /usr/lib64/libm-2.16.so
3cb0000000-3cb00b3000 r-xp 00000000 fd:02 1857565                        /usr/lib64/libkabc.so.1.2.0
3cb00b3000-3cb02b3000 ---p 000b3000 fd:02 1857565                        /usr/lib64/libkabc.so.1.2.0
3cb02b3000-3cb02ba000 r--p 000b3000 fd:02 1857565                        /usr/lib64/libkabc.so.1.2.0
3cb02ba000-3cb02bd000 rw-p 000ba000 fd:02 1857565                        /usr/lib64/libkabc.so.1.2.0
3cb02bd000-3cb02be000 rw-p 00000000 00:00 0
3cb0400000-3cb0416000 r-xp 00000000 fd:02 1837828                        /usr/lib64/libresolv-2.16.so
3cb0416000-3cb0615000 ---p 00016000 fd:02 1837828                        /usr/lib64/libresolv-2.16.so
3cb0615000-3cb0616000 r--p 00015000 fd:02 1837828                        /usr/lib64/libresolv-2.16.so
3cb0616000-3cb0617000 rw-p 00016000 fd:02 1837828                        /usr/lib64/libresolv-2.16.so
3cb0617000-3cb0619000 rw-p 00000000 00:00 0
3cb0800000-3cb0823000 r-xp 00000000 fd:02 1857564                        /usr/lib64/libkresources.so.1.2.0
3cb0823000-3cb0a23000 ---p 00023000 fd:02 1857564                        /usr/lib64/libkresources.so.1.2.0
3cb0a23000-3cb0a26000 r--p 00023000 fd:02 1857564                        /usr/lib64/libkresources.so.1.2.0
3cb0a26000-3cb0a27000 rw-p 00026000 fd:02 1857564                        /usr/lib64/libkresources.so.1.2.0
3cb0c00000-3cb0c35000 r-xp 00000000 fd:02 1838205                        /usr/lib64/liblcms.so.1.0.19
3cb0c35000-3cb0e34000 ---p 00035000 fd:02 1838205                        /usr/lib64/liblcms.so.1.0.19
3cb0e34000-3cb0e35000 r--p 00034000 fd:02 1838205                        /usr/lib64/liblcms.so.1.0.19
3cb0e35000-3cb0e36000 rw-p 00035000 fd:02 1838205                        /usr/lib64/liblcms.so.1.0.19
3cb0e36000-3cb0e39000 rw-p 00000000 00:00 0
3cb1000000-3cb103c000 r-xp 00000000 fd:02 1840740                        /usr/lib64/libreadline.so.6.2
3cb103c000-3cb123b000 ---p 0003c000 fd:02 1840740                        /usr/lib64/libreadline.so.6.2
3cb123b000-3cb123d000 r--p 0003b000 fd:02 1840740                        /usr/lib64/libreadline.so.6.2
3cb123d000-3cb1243000 rw-p 0003d000 fd:02 1840740                        /usr/lib64/libreadline.so.6.2
3cb1243000-3cb1245000 rw-p 00000000 00:00 0
3cb1400000-3cb146e000 r-xp 00000000 fd:02 1836952                        /usr/lib64/libmng.so.1.0.0
3cb146e000-3cb166e000 ---p 0006e000 fd:02 1836952                        /usr/lib64/libmng.so.1.0.0Aborted (core dumped)


backtrace_rating: 3
Package: twinkle-1.4.2-19.fc18
OS Release: Fedora release 18 (Spherical Cow)

I tried opening Twinkle SoftPhone after it had previously been configured to point to an internal phone server.

backtrace_rating: 3
Package: twinkle-1.4.2-19.fc18
OS Release: Fedora release 18 (Spherical Cow)

1. yum install twinkle
2. start twinkle from system menu by clicking on it icon


backtrace_rating: 3
Package: twinkle-1.4.2-19.fc18
OS Release: Fedora release 18 (Spherical Cow)

start twinkle

backtrace_rating: 3
Package: twinkle-1.4.2-19.fc18
OS Release: Fedora release 18 (Spherical Cow)

tried to start twinkle for the first time after installing it via yum install. crash happens each time.

backtrace_rating: 3
Package: twinkle-1.4.2-19.fc18
OS Release: Fedora release 18 (Spherical Cow)

I just started twinkle after fresh installation of F18

backtrace_rating: 3
Package: twinkle-1.4.2-19.fc18
OS Release: Fedora release 18 (Spherical Cow)

Running twinkle without any arguments caused this buffer overflow.

backtrace_rating: 3
Package: twinkle-1.4.2-19.fc18
OS Release: Fedora release 18 (Spherical Cow)

I was invoking twinkle from the command line to ensure that it started correctly, but did not.

backtrace_rating: 3
Package: twinkle-1.4.2-19.fc18
OS Release: Fedora release 18 (Spherical Cow)

Priority of this bug is urgent as there is currently no reliable softphone available in Fedora 18, which is really unpleasant.

(In reply to comment #23)
> Priority of this bug is urgent as there is currently no reliable softphone
> available in Fedora 18, which is really unpleasant.

I agree. However: 

a) Upstream is completely dead and has been for many years. 

b) I haven't been able to track down a fix. 

Patches welcome.

Launching Twinkle on Fedora 18 always dump core.

backtrace_rating: 3
Package: twinkle-1.4.2-19.fc18
OS Release: Fedora release 18 (Spherical Cow)

*** Bug 908654 has been marked as a duplicate of this bug. ***

(In reply to comment #24)
> (In reply to comment #23)
> > Priority of this bug is urgent as there is currently no reliable softphone
> > available in Fedora 18, which is really unpleasant.
> 
> I agree. However: 
> 
> a) Upstream is completely dead and has been for many years. 
> 
> b) I haven't been able to track down a fix. 
> 
> Patches welcome.

So perhaps we should drop it from Fedora?

I will be gutted if it will be dropped
It is the only VoIP software which worked fine in almost all imaginable situation or providers

What as I noticed 
If you don't have a config will give you hangs
or if you start it without internet connection ( or filtered by firewall one)

(In reply to comment #29)
> I will be gutted if it will be dropped
> It is the only VoIP software which worked fine in almost all imaginable
> situation or providers
> 
> What as I noticed 
> If you don't have a config will give you hangs
> or if you start it without internet connection ( or filtered by firewall one)

so there is a workaround to launch it?

I get the crash with or without config.

I didn't try without any network connection though.

twinkle crashed on Fedora 18

backtrace_rating: 3
Package: twinkle-1.4.2-19.fc18
OS Release: Fedora release 18 (Spherical Cow)

(In reply to comment #24)
> (In reply to comment #23)
> > Priority of this bug is urgent as there is currently no reliable softphone
> > available in Fedora 18, which is really unpleasant.
> 
> I agree. However: 
> 
> a) Upstream is completely dead and has been for many years. 
> 
> b) I haven't been able to track down a fix. 
> 
> Patches welcome.

I hope this bug will be fixed,but as alreday written - upstream abonded twinkle ... so let's hope Fedora will not!

While this is a bug that should be fixed upstream, I found a workaround that allows end users to use twinkle as long as there's not real fix: make sure your hostname can be resolved through dns. Having your hostname listed in /etc/hosts is not enough.

Only if the command "host $(hostname)" gives a valid answer, I can start twinkle. So I fixed this by putting my hostname in my routers DNS server.

Hope this helps you guys. Btw, I'm running FC18.

(comment #34) > works for me

(In reply to comment #34)
> While this is a bug that should be fixed upstream, I found a workaround that
> allows end users to use twinkle as long as there's not real fix: make sure
> your hostname can be resolved through dns. Having your hostname listed in
> /etc/hosts is not enough.
> 
> Only if the command "host $(hostname)" gives a valid answer, I can start
> twinkle. So I fixed this by putting my hostname in my routers DNS server.
> 
> Hope this helps you guys. Btw, I'm running FC18.

This workaround is wonderful.  It works in that twinkle starts and I can dial and do hear the dialing out etc. But the audio from me to the other end is OK, but I don't hear anything from the other side. My speakers work fine - I can hear the ringing on the other side but the audio back is not there.

Any suggestions on tracing that return audio channel?

(In reply to comment #36)
> (In reply to comment #34)
> > While this is a bug that should be fixed upstream, I found a workaround that
> > allows end users to use twinkle as long as there's not real fix: make sure
> > your hostname can be resolved through dns. Having your hostname listed in
> > /etc/hosts is not enough.
> > 
> > Only if the command "host $(hostname)" gives a valid answer, I can start
> > twinkle. So I fixed this by putting my hostname in my routers DNS server.
> > 
> > Hope this helps you guys. Btw, I'm running FC18.
> 
> This workaround is wonderful.  It works in that twinkle starts and I can
> dial and do hear the dialing out etc. But the audio from me to the other end
> is OK, but I don't hear anything from the other side. My speakers work fine
> - I can hear the ringing on the other side but the audio back is not there.
> 
> Any suggestions on tracing that return audio channel?

You are missing one leg of the RTP stream. If you are behind NAT, make sure the server knows that. If I am not mistaken, in asterisk that would mean including nat=yes in the definition of your extension.

(In reply to comment #37)
> (In reply to comment #36)
> > (In reply to comment #34)
> > > While this is a bug that should be fixed upstream, I found a workaround that
> > > allows end users to use twinkle as long as there's not real fix: make sure
> > > your hostname can be resolved through dns. Having your hostname listed in
> > > /etc/hosts is not enough.
> > > 
> > > Only if the command "host $(hostname)" gives a valid answer, I can start
> > > twinkle. So I fixed this by putting my hostname in my routers DNS server.
> > > 
> > > Hope this helps you guys. Btw, I'm running FC18.
> > 
> > This workaround is wonderful.  It works in that twinkle starts and I can
> > dial and do hear the dialing out etc. But the audio from me to the other end
> > is OK, but I don't hear anything from the other side. My speakers work fine
> > - I can hear the ringing on the other side but the audio back is not there.
> > 
> > Any suggestions on tracing that return audio channel?
> 
> You are missing one leg of the RTP stream. If you are behind NAT, make sure
> the server knows that. If I am not mistaken, in asterisk that would mean
> including nat=yes in the definition of your extension.

Yes, I am connected to the server via a NAT and the NAT setting is "NAT-T when available (default)".  Switched it to "NAT-T always" and no difference. It's connecting to a Cisco switch I think (I will check that).

(In reply to comment #34)
> While this is a bug that should be fixed upstream, I found a workaround that
> allows end users to use twinkle as long as there's not real fix: make sure
> your hostname can be resolved through dns. Having your hostname listed in
> /etc/hosts is not enough.
> 
> Only if the command "host $(hostname)" gives a valid answer, I can start
> twinkle. So I fixed this by putting my hostname in my routers DNS server.
> 
> Hope this helps you guys. Btw, I'm running FC18.

i re-installed my laptop.
no idea why, but twinkle works now (holding my fingers it will continue...)

same version as before, not related to the workaround:
rpm -qa | grep twinkle
twinkle-1.4.2-19.fc18.x86_64

host $(hostname)
Host localhost.localdomain not found: 3(NXDOMAIN)

no idea what changed.

This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Sorry but in Fedora 19 it seems that twinkle is not any more in repo

look also at

https://bugzilla.redhat.com/show_bug.cgi?id=981171



I was forced to switch to linphone ( not the happiest switch but at least it works)