FS#26500 - [twinkle] segfaults (and no sign of upstream)

Attached to Project: Community Packages
Opened by Johan Vervloet (johanv) - Tuesday, 18 October 2011, 06:39 GMT
Last edited by Sergej Pupykin (sergej) - Wednesday, 16 May 2012, 21:30 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Sergej Pupykin (sergej)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: When I start Twinkle on the command line, I get this message:

terminate called after throwing an instance of 'int'
Aborted

Additional info:
* package version(s)
* twinkle 1.4.2-11
* boost-libs 1.47.0-2
* commoncpp2 1.8.1-2
* file 5.09-1
* libsndfile 1.0.25-1
* libx11 1.4.4-1
* libxml2 2.7.8-1
* libzrtpcpp 1.4.2-5
* qt3 3.3.8-20
* speex 1.2rc1-2

* config and/or log files etc.

Nothing special. If I remove ~/.twinkle, Twinkle starts, but it crashes after the initial configuration. (same error messages)

Steps to reproduce:

* Start Twinkle
This task depends upon

Closed by  Sergej Pupykin (sergej)
Wednesday, 16 May 2012, 21:30 GMT
Reason for closing:  Won't fix
Additional comments about closing:  moved to aur
Comment by Alexander F. Rødseth (xyproto) - Tuesday, 18 October 2011, 08:43 GMT
Confirmed. Segfaults here as well.
Comment by Alexander F. Rødseth (xyproto) - Tuesday, 18 October 2011, 08:53 GMT
Does not segfault here when run with gdb. (x86_64)
Comment by Sergej Pupykin (sergej) - Tuesday, 18 October 2011, 09:20 GMT
I created IP to IP profile and it does not crashes on x86_64
Comment by Johan Vervloet (johanv) - Tuesday, 18 October 2011, 10:52 GMT
In my case I have to connect to our VOIP server. I cannot test IP to IP ATM.
Comment by José Illescas Pérez (yoburtu) - Thursday, 17 November 2011, 18:35 GMT
Is there any solution at this problem?.

Twinkle works correctly in my Arch64 in PC of the work site, but don't work in my Arch64 in PC of home.

Regards.
Comment by Alexander F. Rødseth (xyproto) - Friday, 13 January 2012, 12:18 GMT
The twinkle webpage mentions the following configuration options:
./configure --without-kde
./configure --without-ilbc
./configure --without-speex
./configure --without-zrtp

The PKGBUILD depends on the following:
depends=('file' 'speex' 'boost-libs' 'libsndfile' 'commoncpp2' 'libxml2' 'libx11'
'qt3' 'libzrtpcpp')

Just a shot in the dark, but does "ilbc" have the required dependencies installed?
Comment by Sergej Pupykin (sergej) - Monday, 16 January 2012, 09:27 GMT
ilbc is in aur (https://aur.archlinux.org/packages.php?ID=2963) so I rebuilt twinkle --without-ilbc.

Please try 1.4.2-13.
Comment by Alexander F. Rødseth (xyproto) - Tuesday, 24 January 2012, 12:54 GMT
Still segfaults here:
terminate called after throwing an instance of 'int'
[1] 26144 abort (core dumped) twinkle

twinkle 1.4.2-13
Comment by Alexander F. Rødseth (xyproto) - Saturday, 04 February 2012, 00:34 GMT
Is this an upstream bug?
Comment by Alexander F. Rødseth (xyproto) - Friday, 10 February 2012, 12:04 GMT
Are commoncpp2, ccrtp and twinkle built with the same version of gcc? (Ref. the FAQ at http://mfnboer.home.xs4all.nl/twinkle/)
Comment by Alexander F. Rødseth (xyproto) - Sunday, 12 February 2012, 19:28 GMT
Updated and rebuilt commoncpp2, ccrtp and twinkle with gcc 4.6.2. Twinkle still segfaults.
Comment by Alexander F. Rødseth (xyproto) - Wednesday, 22 February 2012, 14:05 GMT
Couldn't find a bug tracker, but contacted the maintainer (michel _at_ twinklephone _dot_ com). Awaiting reply.
Comment by Alexander F. Rødseth (xyproto) - Monday, 27 February 2012, 07:46 GMT
I contacted Michel the 10th of february and the 22nd of february, but has not received a reply yet.

Since twinkle appears to be unmaintained and has bugs that causes segfaulting, I suggest moving it to unsupported.
Comment by Alexander F. Rødseth (xyproto) - Sunday, 04 March 2012, 19:25 GMT
This bug has been open for 138 days now, and no sign of upstream. It's obviously unsupported. Do you mind if I move it to unsupported?
Comment by Sergej Pupykin (sergej) - Monday, 05 March 2012, 00:54 GMT
The single reason why I did not it yet is that it works on my machine
Comment by Alexander F. Rødseth (xyproto) - Monday, 05 March 2012, 01:19 GMT
I see. Is that even after removing ~/.twinkle?

If it works for you and you wish to keep it, that's understandable, but it's not a good sign that upstream is unavailable.
Comment by Sergej Pupykin (sergej) - Wednesday, 16 May 2012, 21:30 GMT
finally I moved twinkle to aur (https://aur.archlinux.org/packages.php?ID=59294) because of it is not compatible with current rtp libraries

Loading...