(In reply to comment #1)
> using HTTP Connect on any port that is not 443 has a big chance of being
> denied by sys-admin.
Do you have any statistics of how many sys-admins deny that? Or *any
evidence* for that claim?
> To me this is a bug in libpurple.
It's not. As you can see from the Ubuntu b
"Empathy" has nothing to do with proxy stuff, connection issues and so
on. You need to check which specific telepathy CM you are using. That
should be easy to check with 'ps -A | grep telepathy'. My guess would be
that only telepathy-haze works (using GNOME's proxy settings).
--
Does not use syst
libpurple has support for video, all telepathy-haze has to do is
implement the wrapper from libpurple to telepathy... but that's not
implemented yet (perhaps never).
--
Does not use system proxy settings
https://bugs.launchpad.net/bugs/304889
You received this bug notification because you are a m
@papukaija But that's the problem; GNOME guys don't want to implement
HTTP Connect in GIO, and libproxy guys interpret gnome-network-
properties wrongly. So in reality HTTP Connect is not supported at all,
nor is it planned to any time soon. But that's ok according to the
developers, because "less
> But there is nothing to be done for Empathy itself here -- so it is
Invalid as a bug task.
This is not true. The upstream "support" would just use the GNOME proxy
settings, and it would not be possible to configure the proxy per-
account, for that you would still need changes in Empathy.
If you
C de-Avillez:
First of all, let's remember that you don't have to fix all the CM's to
fix this issue. Ubuntu can fix this *today*, regardless of the status of
the telepathy CM's
(1) This is pointless, because a) it's not needed, and b) each CM has
different issues regarding proxy support.
* tele
On Wed, Nov 30, 2011 at 6:37 PM, Guillaume Desmottes wrote:
> Le mercredi 30 novembre 2011 à 15:55 +0000, Felipe Contreras a écrit :
>> * telepathy-haze
>>
>> This works fine.
>
> Stop claiming that switching to Haze is the solution of all the world's
>
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.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to empathy in Ubu
I already explained many times how to fix this *right now* (in fact more
than one year ago). See comment #76.
The fact of the matter is that Ubuntu people don't care, otherwise they
would have marked it as critical as I suggested in comment #79. "It will
be on the next release cycle" somebody said
Commit rights are irrelevant. Nobody has commit rights in the Linux
kernel except Linus. Does that mean everybody else's opinion don't
matter.
See comment #92, #93 and #94; the fix is known to work.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is s
@Michael telpathy-haze has support for IRC too.
AIM, facebook, gadugadu, groupwise, IRC, ICQ, jabber, local XMPP, MSN,
QQ, sametime, sipe, yahoo, zephyr, mxit, and sip; IOW what libpurple
(Pidgin) supports.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, wh
@Brian No, proxy support works on gabble only for certain kinds of
configurations. For example a global HTTP proxy doesn't work. See
comment #118.
haze is *not* a libpurple implementation, and telepathy *does have*
control over that.
And what do you mean "can't allow popups for password questions
No, telepathy-haze is just another Telepathy Connection Manager. Read
the text you just shared:
Haze: A connection manager based on Pidgin's libpurple, supporting all
protocols in Pidgin (AIM, ICQ, Yahoo, MSN, etc) at a basic level, but
already very usable.
libpurple uses GConf's system proxy set
Small update.
Some Telepathy CM's such as gabble (XMPP) and butterfly (MSN) now have
some proxy support, however, they depend on libproxy doing the right
thing (which it usually doesn't). So essentially they still don't work.
A more generic solution should be implemented in GLib, however, they ar
@Guilliame Right, *if* you have at least GLib 2.26, and *if* you have
the corresponding glib-networking (which is not packaged in Ubuntu), and
*if* you have libproxy 0.4.6 (0.3.1 in Ubuntu), and *if* you have the
exact right configuration in GConf (not "Use the same proxy for all
protocols"), and *
@Nicolas
> But the fact is that this method had never worked.
Grep for "pidgin" in this thread. That method works. In fact, it's the
only one that does. That's why this bug exists and people are annoyed;
the default IM client used to work (Pidgin), now it doesn't (Empathy).
What I would have don
> How about people following this bug mention what type of proxy support they
> need? (socks, http, etc.)
Personally, my university (Tec Monterrey), and the companies I've worked
for (Texas Instruments, and Nokia), they all have used an HTTP proxy for
everything (HTTP Connect). And all the proxy
FTR. I've been pushing Pidgin devs to implement this since a long time ago.
Latest try with patch is here:
http://pidgin.im/pipermail/devel/2010-January/009177.html
On 2.7.0 the API seems to be there, but even if telepathy-haze utilizes
it, it would only work for MSN; for other protocols you need
First of all, GNOME never switched from Pidgin to Empathy because Pidgin
has never been part of GNOME, and has never intended to. It's just a
GTK+ app that has never collaborated with anyone... GNOME,
freedesktop.org, etc. So, before Empathy, GNOME didn't really have an
alternative.
Now, I think d
Guillaume: here's a technical argument: Empathy doesn't work.
That's a blocker. As long as the bug is not blocker, the best thing
users can do is complain. Once the bug is marked as blocker, then
there's no point in users complaining since developers are already aware
of the importance of the bug.
Sebastien: the fact that you are unwilling to fix a critical bug doesn't
make it any less critical.
"will be handled in the next cycle" yeah, right... you are relying on
upstream, so it might not. Or do you have a timeline when it will be
fixed for all protocols that somehow fits Ubuntu's plan?
S
21 matches
Mail list logo
