Marc, hi,

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'm not pretending to maintain twinkle (I don't) but none of the other members of the VoIP team have said anything about experiencing this bug, so I'd love your feedback on this!

Marcus, you raised the severity to RC and marked the bug as found on 1:1.2-1 but didn't explain why. Are you experiencing this bug or are you marking it based on previous reports?

Mikael, you did all the changes in the last upload. Mark Purcell who was maintaining this package inside the VoIP team is MIA for some time due to personal reasons and I haven't even used twinkle, ever!
Can you handle this please?

If not, can someone else from the team step up and maintain twinkle?
This is a quite popular package, we shouldn't pretend to maintain it if we really are not.
If noone steps up in a week or so, I'll file an RFH or even O bug.

[forgive my rants, but I just read that twinkle will be removed from testing in the next britney run]

Thanks,
Faidon



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to