On Wed, Mar 19, 2008 at 11:22:57PM +0200, Faidon Liambotis wrote: > Marc Haber wrote: > >I get an incoming call. THe call is established, but I cannot hear the > >caller and the caller cannot hear me. This _might_ be caused by my > >broken home router which does not NAT correctly (the ISP claims that > >VoIP is not supported on what they call "Internet Access", and I > >cannot exchange the router for something else). > > > >However, when that "call" terminates, twinkle freezes. The Clock on > >the right side of the "Line 1" panel simply stops, the detail display > >still says "Call established", and twinkle does not react to anything. > >I only can click on the "Close Window" button and tell kwin to > >terminate the app. > We got a report from a user that was facing a very similar problem -if > not the same- that the bug is fixed in the current version of twinkle. > > According to that user, Jim Thomas, the fix may be related to a KDE > upgrade -- perhaps it was not a twinkle bug in the first place.
I just did a few calls, incoming and outgoing, and didn't see twinkle crashing. All calls were connected bi-directional just as they should be. I hope it'll stay that way. Twinkle 1:1.2-1 on a current Debian unstable. Greetings Marc -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 3221 2323190 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]