After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 653009 - Ekiga will crash if it receive a call from NetMeeting
Ekiga will crash if it receive a call from NetMeeting
Status: RESOLVED FIXED
Product: ekiga
Classification: Applications
Component: Call stack
3.2.x
Other Linux
: Normal critical
: ---
Assigned To: Ekiga maintainers
Ekiga maintainers
Depends on:
Blocks:
 
 
Reported: 2011-06-20 13:59 UTC by Nicolas Sapa
Modified: 2012-10-20 21:52 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
script of the gdb session (80.07 KB, text/plain)
2011-09-05 17:52 UTC, Nicolas Sapa
Details
script of the gdb session - ekiga 3.3.1 (42.09 KB, application/octet-stream)
2011-09-06 14:59 UTC, Nicolas Sapa
Details

Description Nicolas Sapa 2011-06-20 13:59:37 UTC
Calling Ekiga from NetMeeting will crash Ekiga (UTF-8 Parsing issue ?):
[nico@Gallifrey ~]$ ekiga

(ekiga:30199): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: Erreur à la ligne 1, caractère 77 : Codage UTF-8 non valide dans le nom - «  Microsoft\xae NetMeeting\xae	3.0	181/21324	 » n'est pas valide

(ekiga:30199): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: Erreur à la ligne 1, caractère 77 : Codage UTF-8 non valide dans le nom - «  Microsoft\xae NetMeeting\xae	3.0	181/21324	 » n'est pas valide
[nico@Gallifrey ~]$ 

Ekiga 3.2.7 from Fedora 14
Comment 1 Eugen Dedu 2011-09-05 16:38:48 UTC
Sorry to answer so late.  Could you please send us a gdb stacktace?  It is very simple, see http://wiki.ekiga.org/index.php/Debugging_Ekiga#How_to_get_a_stack_backtrace_from_a_crash
Comment 2 Nicolas Sapa 2011-09-05 17:52:38 UTC
Created attachment 195724 [details]
script of the gdb session
Comment 3 Nicolas Sapa 2011-09-05 18:08:13 UTC
I set a breakpoint for g_logv in order to get a backtrace.
If it isn't sufficient, please tell me on what i should break ...
Comment 4 Eugen Dedu 2011-09-05 19:20:05 UTC
I see the line generating the problem, thank you.

The simplest thing for me is to see if it still happens with current release.  Is it possible to you to call me (eugen.dedu@ekiga.net) with netmeeting?
Comment 5 Nicolas Sapa 2011-09-05 22:33:31 UTC
Installed Packages
Name        : ekiga
Arch        : x86_64
Version     : 3.2.7
Release     : 4.fc14


Do you wish that I try with ekiga 3.3.1 ?
I can try to backport it from Fedora 17.
Comment 6 Eugen Dedu 2011-09-06 10:21:12 UTC
Yes, please check with 3.3.1.  If it works, tell if the name is correctly written in the call dialog box.  If it does not work, send a gdb output to see if it crashes at the same place.

I have just checked and it does not crash here.
Comment 7 Nicolas Sapa 2011-09-06 14:59:08 UTC
Created attachment 195790 [details]
script of the gdb session - ekiga 3.3.1
Comment 8 Nicolas Sapa 2011-09-06 15:23:52 UTC
Still crashing with:

Installed Packages
Name        : ekiga
Arch        : x86_64
Version     : 3.3.1
Release     : 3.fc14
Comment 9 Eugen Dedu 2011-09-06 16:29:21 UTC
Ok, I wait for someone's answer and I fix it, thank you.
Comment 10 Eugen Dedu 2011-09-12 17:16:01 UTC
Ok, I had the answer.  It seems to me that NetMeeting puts in User-Agent a string invalid in utf-8 (probably in latin-1 encoding).  I want to be sure about the encoding, so that I try a conversion if possible.  For that, could you be kind to send me:
- from 'ekiga -d 4' log only the line containing NetMeeting (using grep for example)
- from wireshark capture, the packet containing this string, more precisely I want to know what is the "wrong" character (which encoding is it used for it?)

Could you do it or it is too complicated?
Comment 11 Eugen Dedu 2012-10-20 21:52:07 UTC
Closed, sorry for the long delay!  http://git.gnome.org/browse/ekiga/commit/?id=7d09807257.