Olleg Samoylov wrote:
Log is attached
Hi, The problem is that somehow the port is set to 0. I'm sorry to say, but developers consider gtk-only for 2.0.x as not being sufficiently stable to use it. And, as they work hard for the upcoming 3.0 release, they don't consider useful to fix this bug:
Why do these people switch from "normal" ekiga to ekiga-gtkonly? Of course when doing that the configuration can no longer be read from gconf. I do not even know that the gtkonly version of 2.0.12 is completely workable anyway...
As debian is in freeze, I see two solutions: - either remove gtkonly version for 2.0.x release - either do not consider this bug as an RC bug Please let me know if I am wrong or what I can do. -- Eugen Dedu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
