[Bug 1024529] [NEW] Update needed to get Call working
Public bug reported: Tp-Glib should at least be updated to 0.8.1 in order to make the call works. Though, I recommended tracking the stable 0.8 branch, current stable is 0.8.3. ** Affects: telepathy-glib (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1024529 Title: Update needed to get Call working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-glib/+bug/1024529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 540536]
Added CM's name to the title, to help sorting. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/540536 Title: Empathy does not support AIM buddy chat To manage notifications about this bug go to: https://bugs.launchpad.net/telepathy-haze/+bug/540536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 304889]
Telepathy Butterfly (MSN) already supports SOCKS5 and HTTP Connect proxy with authentication. I'm working on adding HTTP Connect proxy to Wocky (while SOCKS5/4a/4 is provided by GLib 2.26 and newer). I suggest we attach dependency to this bug for tracking. Contrary to what Pidgin do, Telepathy connection manager rely on system proxy settings only for now (which are optained using libproxy). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/304889 Title: Does not use system proxy settings To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/304889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 304889]
(In reply to comment #3) Correct me if I'm wrong, but GNOME 3 proxy settings don't have any fields to enter the authentication information, so Simon McVittie's option (a) is not currently possible. Simon comment was posted in 2008, Gnome 3 didn't yet exist to make proxy support worst. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/304889 Title: Does not use system proxy settings To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/304889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 745803] Re: telepathy logger uses 100% CPU
I confirm this one, which should be fixed by http://cgit.freedesktop.org/telepathy/telepathy- logger/commit/?id=884c52dad5d5fb30a450b013b83aed306ed49164 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/745803 Title: telepathy logger uses 100% CPU -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 725512] Re: telepathy-logger crashed with SIGSEGV in free()
Just an update, another case of the same crash type was found and fixed, try updating to latest 0.2.5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/725512 Title: telepathy-logger crashed with SIGSEGV in free() -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 728302] Re: telepathy-logger crashed with SIGSEGV in strchr()
Omer Akram, sorry if that message was a little unclear, I meant correctly giving details to freedesktop.org bug next time. I released 0.2.5 that should address a crasher similar to your issue, so please update. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/728302 Title: telepathy-logger crashed with SIGSEGV in strchr() -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 728302] Re: telepathy-logger crashed with SIGSEGV in strchr()
Just a reminder, you backtrace does not contain debug symbols, and you opened an upstream bug without the basic information: 1) Instruction to reproduce 2) System architecture (32bit/64bit if Intel) 3) Dependency version, especially GLib in this case Note that I'm trying to be kind now, but we usually don't like to go back and forth from freedesktop bugzilla to launchpad bug system. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/728302 Title: telepathy-logger crashed with SIGSEGV in strchr() -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 304889] Re: Does not use system proxy settings
When I first started working on proxy in Telepathy there was two ways this could be fixed. The quick way would have been to implement it in every single network oriented application. To do so you just have to find another project that match licence, copy paste some code do basic testing and your done. But the fact is that this method had never worked. The big portrait is that every software interpret the configuration differently (mainly due to ambiguities in the configuration) or has incomplete implementation. I was bored of that, so I took the long road, that one that can benefit all and eventually ensure that network oriented application don't have to care about proxy since it will just work. This road is to get proxy support to be handled by libraries like GIO and libproxy. In contrast to what Felipe says, having to update things into distribution to get things to work is completely normal, and takes time. We can't implement features in already existing versions and we can't maintain hundreds of different branches of every projects so the distro does not have to update. Getting this in the next Ubuntu release has nothing to do about doubt, it's about priority. If 100% of the targeted users where using HTTP Connect proxy, all this would be updated much faster. But the reality is that HTTP Connect users represent probably less then 1% of the users, I don't think it's enough people to justified the risk and the energy required to get those new features in so quickly. What you should do instead if you have the knowledge and time is to test those things, discuss and report precise bugs and create testimonial for distro that says it's working. Finally, Telepathy Butterfly (the MSN backend) has full HTTP/HTTP Connect/SOCKS support. I don't know where Felipe got that it does not work for MSN because it works very well. What Felipe is confusing in his comment is the support for proxy in Telepathy against bugs in the libproxy implementation. Yes HTTP Connect is considered an unsafe choice in libproxy. HTTP Connect server (the commercial ones) has a large reputation of implementing filters and port blocking that usually reduces your connectivity. We are working hard to make it possible to trigger this choice in libproxy without the risk of reducing your connectivity, but we have hit an internal design issue that needs more time. Felipe also often ignore the miss-adapted configuration tool we have in Gnome. This tool, based on old Netscape Navigator configuration, is undocumented and present ambiguities. On this, some people also have long term solution like a new storage for GSettings/GConf or even an integration with software like NetworkManager or ConnMan. But let me reassure you that as soon as the previously mentioned bug in libproxy is fixed, I'm also going forward with shorter term fixes that should make it work better. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/304889 Title: Does not use system proxy settings -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
