ekiga crashes on forwarded incoming call

Bug #735473 reported by stegy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ekiga (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: ekiga

1) lsb_release -rd
Description: Ubuntu 10.10
Release: 10.10

2)apt-cache policy ekiga
ekiga:
  Installiert: 3.2.7-2ubuntu1
  Kandidat: 3.2.7-2ubuntu1
  Versionstabelle:
 *** 3.2.7-2ubuntu1 0
        500 http://de.archive.ubuntu.com/ubuntu/ maverick/universe i386 Packages
        100 /var/lib/dpkg/status

3) All Asterisk sip users with no Umlauts in the name-field can call me.

4) Incoming calls with umlauts in the name-field causes ekiga to crash with:

(ekiga:23511): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: Fehler in Zeile 1, Zeichen 51: Ungültiger UTF-8-kodierter Text im Namen - »Test T\xe4st« ist nicht gültig

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: ekiga 3.2.7-2ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8
Uname: Linux 2.6.35-24-generic i686
NonfreeKernelModules: brusbmfc nvidia
Architecture: i386
Date: Tue Mar 15 14:22:50 2011
ExecutablePath: /usr/bin/ekiga
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: ekiga
XsessionErrors:
 (polkit-gnome-authentication-agent-1:1664): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (gnome-panel:1662): GConf-WARNING **: Directory `/apps/panel/toplevels/bottom_panel_screen1/screen' was not being monitored by GConfClient 0x8696f58
 (gnome-panel:1662): GConf-WARNING **: Directory `/apps/panel/toplevels/top_panel_screen1/screen' was not being monitored by GConfClient 0x8696f58
 (tomboy:1667): Gtk-CRITICAL **: gtk_ui_manager_remove_action_group: assertion `g_list_find (self->private_data->action_groups, action_group) != NULL' failed

Revision history for this message
stegy (stegy) wrote :
Revision history for this message
Eugen Dedu (eugen-dedu) wrote :

This was fixed right before ekiga 4.0.0, so please try out that version.

Changed in ekiga (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.