[Bug 304889]
(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 bug: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/304889 There's *plenty* of people that want this behavior. Empathy should provide an option to configure the proxy *per account*, just like Pidgin does -- 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 371897]
(In reply to Ben Klein from comment #404) > (In reply to Ben Shadwick from comment #403) > > The Wine devs are so irrationally close-minded about this issue > > OK, stop there before this descends into a flame-war. Stop what? To me this seems to be an accurate description of the actual issue we are facing here. Ignoring the real issue is not going to get us anywhere. > > citing of silly procedural issues as an excuse to avoid having > > to incorporate fixes. > > Those "procedural issues" relate to code quality and cooperative > functionality with other modules. Winepulse is not up to scratch. I haven't been very involved in the Wine community, but I do recall another bug report about dwrite breaking Steam because it wasn't yet working correctly. Not only was the dwrite code in the source tree, it was enabled by default (it shouldn't be). If incomplete code known to break important applications is part of source tree, why isn't wine pulse there? You say there are some "issues" with it. Sure, I can believe there are issues, however, code doesn't have to be perfect in order to be merged. Most code is merged after all the obvious issues found in code review are addressed, sometimes with known issues and TODO's. Eventually one by one the issues are addressed. Not merging the code because it's not "perfect" is irrational, and that's a fact. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/371897 Title: Occasional sound drops in Wine via PulseAudio To manage notifications about this bug go to: https://bugs.launchpad.net/wine/+bug/371897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 422926] Re: MSN chat broken; crashes pidgin
** No longer affects: msn-pecan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/422926 Title: MSN chat broken; crashes pidgin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/msn-pecan/+bug/422926/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 521877]
(In reply to comment #27)
> On Tue, Feb 16, 2010 at 10:58:07PM -0800, bugzilla-dae...@freedesktop.org
> wrote:
> > --- Comment #26 from Andrey Rahmatullin 2010-02-16
> > 22:58:04 PST ---
> > (In reply to comment #20)
> > > It was chosen in order to make display of web pages using Xorg more
> > > consistent
> > > with the way they get displayed on Windows, which by default assumes 96.
> >
> > Is it an official position of X.org developers? Is it documented anywhere?
>
> Sure, consider it an official position. I don't think it's
> unreasonable. Especially if you assume that lower-DPI displays are
> likely to be higher-resolution and thus physically huge, meaning that
> people sit further away from them, and that displays with a meaningfully
> higher DPI are almost always found in phones (as well as some laptops)
> these days, meaning that people hold them a great deal closer to their
> face.
>
> I do agree that being able to configure the reported DPI (or just Option
> "DontForce96DPI") would be entirely useful, but I can't see us changing
> anything in the near future, particularly if it breaks web page display.
> Saying 'well, don't go to that website then' isn't helpful to anyone at
> all, and makes us look like we value strict technical correctness ('but
> don't you know what the true definition of a point is?!?') over an
> actual working system. While we do value strict technical correctness,
> we don't value it to the point of crippling everything else.
Why are you trying to fix browser bugs in X?
If you want to fake the DPI to 96, that should be a configuration in
XRandr, or something, that people can easily disable, but it would be a
workaround, not a fix.
Setting a fixed DPI is completely and totally the wrong thing to do.
Say, my laptop's display has a DPI of 142, and then I plug my display of
101 DPI, the fonts will look completely different, and I would be forced
to change the font settings (if there are any).
Do you seriously think that people changing their font settings each
time they plug/unplug external displays is ideal?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/521877
Title:
[gm45] wrong screen size detected on X200s
To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/521877/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 304889]
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 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
Re: [Bug 304889] Re: Does not use system proxy settings
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 > problems. Haze can be an option for protocols not having a proper CM but > it would be completely stupid to switch to it for XMPP: no call, no file > transfer, no muc, no desktop sharing... Being able to log in is more important than anything else. >> * telepathy-butterfly >> >> It uses papyon, which looks like it's going to be discontinued. It has >> basic proxy support, but it's not done through GIO, as it probably >> should be. > > I agree that Haze could be used. Actually we're going to switch to Haze > for MSN accounts in 3.4 as butterfly (and the other Python CMs) are not > properly maintained and lake all the recent Telepathy APIs. Makes sense. >> * telepathy-gabble >> >> Seems to have proxy support through GIO, but there are issues. > > Which issues exactly? Are there in Gabble? in GIO? All the issues related to libproxy for starters, like not being able to get a popper configuration with GNOME 2, and thus all the DE's that already rely on those GConf settings, like Xfce. And all the issues related to GNOME 3 configuration, like the fact that all authentication is missing. Plus, in my machine, even with GNOME 3's control center it's confusing what should be the settings, and even when I put exactly the right settings, it takes a long long time to log in. >> * telepathy-idle >> >> No proxy support on the horizon. > > Idle has switched to GIO (fdo #37145) so SHOULD be at the same state as > Gabble. Yes, many things should be in certain way *in theory*, but then why is fdo #12376 still open? Because nobody has actually tried *in practice*. Here, let me try... Nope... doesn't work. What a surprise. >> * telepathy-rakia >> >> No proxy support on the horizon. Or bug report about it. > > Please feel free to open one. Why would I do that? As I stated multiple times, this is not *needed* to solve the issue at hand. You can disagree all you want with me, but the fact of the matter is that after more than 3 years this bug has existed, the issue remains there, and users are *completely* prevented to use Empathy. This is the problem going the GNOME way of trying to have everything perfectly. When is that going to happen? 2020? -- Felipe Contreras -- 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] Re: Does not use system proxy settings
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. * telepathy-haze This works fine. * telepathy-butterfly It uses papyon, which looks like it's going to be discontinued. It has basic proxy support, but it's not done through GIO, as it probably should be. * telepathy-gabble Seems to have proxy support through GIO, but there are issues. * telepathy-idle No proxy support on the horizon. * telepathy-rakia No proxy support on the horizon. Or bug report about it. * telepathy-sunshine No proxy support on the horizon. Or bug report about it. Even if you fix all these issues in the connection-managers, this *still* doesn't solve the problem that some people need proxy configuration in a per-proxy way, as explained upstream bug #16034, you would need modifications both in the connection managers, *AND* Empathy. (2) I have already done that: http://thread.gmane.org/gmane.comp.freedesktop.telepathy/4103 Some responses I've heard from upstream developers, are "Nobody uses proxies", "Nobody uses HTTP connect", "Sysadmins probably never allow HTTP connect for non 443 ports", "If you need special proxies for some accounts, write your own PAC file". And similar. The fact of the matter is that they have no urgency to fix this, or even acknowledge the problems. In the meantime, people are completely unable to use Empathy, and are forced to use Pidgin (or use telepathy-haze by removing all the other CM's Ubuntu ships by default). Again, Ubuntu could fix this *today*, it doesn't have to wait for upstream to acknowledge this is an issue. (3) I didn't get that. Pedro Villavicencio: That's only if you use global settings, and as I argued in the response for (1); that's not enough. Upstream bug bug #22065 complains about that, and upstream bug #16034 describes the solution, which requires modifications to Empathy. So, I repeat, do you want to fix this or not? Because you can fix it right now. -- 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] Re: Does not use system proxy settings
> 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 assume this is only to read the system settings, then yes, this is not a bug in Empathy, it has to be implemented in all the telepathy connection managers but the list above (haze, gabble, and idle) is not nearly complete. Plus, none of those bugs have any priority, severity, or even any comment there. At this point it would be useful to do what Fedora does, have keep this bug open as a metabug, or tracking bug, and when all the telepathy CM's are fixed, then this is closed. Moreover, the upstream tracking bugs are wrong. Bug #22065 is not to use system proxy settings in telepathy-haze, in fact, it's for exactly the opposite; have an option to *disable* the proxy for this particular account, for which actually, you would need changes in Empathty. In fact, if you read the comments above in this bug report, you would see that people confirm that telepathy-haze is actually the only one that works. You could fix this bug *today* if you wanted to, by just distributing telepathy-haze, and not the other connection managers. So there's something Ubuntu can do to fix this, but you just don't want to. Bug #16034 has nothing to do with system proxy settings, which supposedly telepathy-gabble already supports (although not that smoothly). It is about user/password authentication to the proxy. Interestingly enough if you read comment #2, a telepathy developer suggests as an option to modify Empathy to allow configuring the proxy settings in a *per account* way: > (b) Empathy gains http-proxy-server, http-proxy-port, http-proxy- username and http-proxy-password parameters in the Advanced area of account config Bug #12376 is correct, but as you can see, there's nothing going on over there. So, do you want to fix this or not? If you want to fix this, then closing the bug is like shuffling it under the carpet... It won't achieve anything. -- 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 780312] Re: msn-pecan cannot connect: nexus stream error
If you are talking about disabling the account while it's trying to connect, you can try picking this patch: https://github.com/felipec/msn-pecan/commit/7f11a66971f7c8df8da9f41bb95353cf77ad806e -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/780312 Title: msn-pecan cannot connect: nexus stream error -- 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
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 settings, which contain authentication. And you have been told wrong, here's a screenshot with the latest gabble not working (latest glib, with glib-networking, with libproxy support): http://people.freedesktop.org/~felipec/gabble-proxy.png See? Works fine with libproxy-simple though. -- 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
[Bug 304889] Re: Does not use system proxy settings
@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"? -- 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
[Bug 304889] Re: Does not use system proxy settings
@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 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
[Bug 304889] Re: Does not use system proxy settings
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 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
[Bug 304889] Re: Does not use system proxy settings
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 as an excuse. And here we are a year later. -- 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
[Bug 304889] Re: Does not use system proxy settings
@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 than 1% use it", according to comment #117. Anyway, I've created my own libproxy-simple, which acts like libproxy, but actually works. Or you could just use telepathy-haze as I've proposed and many people have said here that it Just Works. -- 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
[Bug 304889] Re: Does not use system proxy settings
> 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 bugs I've had in my projects (msn-pecan) have been of HTTP proxies. -- 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
[Bug 304889] Re: Does not use system proxy settings
@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 done is write something that works, like your code for socks and http proxies, and make it a library, or just copy it inside the most popular CM's (gabble and butterfly) with a git submodule. This way you wouldn't be relying on GLib slowness/stubbornness. Once GLib has proper proxy support, you switch. Problem solved. The next problem is configurability. Instead of relying _completely_ on libproxy, I would allow the option to override the proxy configuration with a CM property, this way even if libproxy is buggy (which it is), the user would not be stuck. I would have also added the option to read directly from GConf, and let the user be able to choose this option. > so I took the long road With my proposal you have the benefit of both. When libproxy/GIO are truly ready, you can switch easily, and everyone benefits. In the meantime, things would work, and this bug would be solved. > having to update things into distribution to get things to work is completely > normal Normal for GNOME people. Other people would rather have something working _right now_, even it's not exactly the mode ideal, generic, extensible, and permanent way of doing things. Hint: Pidgin, XChat, Firefox, Ekiga, etc. > But the reality is that HTTP Connect users represent probably less then 1% of the users Ha! I would like to see proof of that. How about people following this bug mention what type of proxy support they need? (socks, http, etc.) It's important because Nicolas is assuming _everyone_ is using SOCKS, and that is reflected on how libproxy interprets GNOME network configuration. > What Felipe is confusing in his comment is the support for proxy in Telepathy > against bugs in the libproxy implementation. Take a look at the title of this bug: use *system* proxy settings. This means GConf, and this means precisely libproxy. If libproxy returns "socks", when the user is expecting "http" (which it does), then the user wouldn't be able to connect, and this bug remains valid. > We are working hard to make it possible to trigger this choice in libproxy > without the risk of reducing your connectivity What you don't seem to understand is that the connectivity is *zero*, you cannot reduce that, even if you try. Note that libproxy is not used by anything in Unbuntu, so it doesn't matter what you do there, it would not affect anyone negatively. The problem is this GNOME mentality, that everything must be perfect since day 0, and therefore it's OK if things don't work at all before that, which is the current situation. > Felipe also often ignore the miss-adapted configuration tool we have in Gnome. Works in Pidgin. Now, I would not like to give the impression that everything is horrible. There is great progress thanks to the efforts of many people, specially Nicolas; we are getting closer and closer to the generic solution, and I certainly would like to contribute to these efforts, when time allows. However, I would like something that works _right now_, and I think everyone here agrees. So, for me, I'm looking into various solutions that are not "perfect" but should get the job done (any of them): a) By default install only telepathy-haze (no gabble, idle, butterfly, etc.) b) Update to libproxy 0.4.6 and apply a patch so it's possible to return both "http" and "socks" for _all_ protocols (msn, xmpp, irc, etc.) I don't think any other option has any chance of making it for the next Ubuntu release. Also, I would like to correct my previous statement that MSN would not work. It does seem that the latest telepathy-butterfly has the option to override whatever libproxy is passing, so it's possible to get it working. However, that would not resolve this bug. Cheers. -- 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
[Bug 304889] Re: Does not use system proxy settings
@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 *if* you have at least telepathy-gabble 0.10.0 (latest Ubuntu does have it); sure, it would work. Currently that's not the case, and I doubt it would be on the next Ubuntu release. However, that's only for XMPP, for other protocols, like MSN, it wouldn't work, more changes are needed in libproxy for that. So no, I wouldn't hold my breath until this bug is fixed. Unless of course all protocols are supported through libpurple (through telepathy-haze), which people here have confirmed. In this case, this bug would be fixed *today*. -- 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
[Bug 304889] Re: Does not use system proxy settings
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 are reluctant to provide HTTP Connect support because it's "unsafe" (no idea what they are smoking). So, as usual with anything GLib, there's progress, but it will take a long long time before it actually works. -- 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
[Bug 404022] Re: Empathy shows my ICQ number instead of my Nickname
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 to file bugs on Pidgin so they implement the functionality there. -- Empathy shows my ICQ number instead of my Nickname https://bugs.launchpad.net/bugs/404022 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- 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
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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- 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
"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 system proxy settings https://bugs.launchpad.net/bugs/304889 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- 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
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? Still, nothing prevents you from marking the bug as critical *right now*, so that it gets the proper attention for the next cycle. You failed to do that in the previous one, and here we are again; it's always too late to do anything. -- Does not use system proxy settings https://bugs.launchpad.net/bugs/304889 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- 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
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. So, either mark the bug as critical, or endure users' complaints. Read the telepathy-haze bug report (22065), libpurple is *already* fetching proxy settings from GConf regardless. IMHO you are not aware of the importance of this bug and not listening either. You are planning for something that's completely irrelevant. Listen to what AbelChiaro said: he needs to *switch off* the proxy settings in GNOME in order to log in to Sametime. Why is that? Because libpurple is reading them and telepathy-haze doesn't provide any way to configure that. He doesn't need proxy support in libpurple (or haze), he needs proxy *configuration* support. So how do we fix this bug? 1) Make proxy settings configurable in telepathy-haze (easy) 2) Prioritize telepathy-haze over other CM's (gabble, idle, butterfly) If Ubuntu guys are ok with 2), I can do 1). -- Does not use system proxy settings https://bugs.launchpad.net/bugs/304889 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- 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
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 distributions should have made proxy support a _blocker_ feature for Empathy inclusion (regardless of GNOME's decision), but that didn't happen, and now people are complaining (understandably) because the default IM client just doesn't work (for them). I don't agree with Guillaume, I think people have a reason to complain, but it would be nice to do it in a more constructive manner, and perhaps follow the upstream bugs, and perhaps provide some testing. However, the upstream bugs are very scattered and unclear. For example, telepathy-haze *already* has proxy support since libpurple already has proxy support, however, it works mostly by accident, behind the back of telepathy-haze using GConf. All Telepathy guys need to do is add some configuration to pass to libpurple, and use telepathy-haze instead of native CM's. Unfortunately, for political reasons I doubt Telepathy guys would do that, instead they will wait until their native CM's do support proxy properly. If Ubuntu guys are interested, I'm sure I can provide patches for that. -- Does not use system proxy settings https://bugs.launchpad.net/bugs/304889 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 422018] Re: Downgrade msn-pecan in karmic down to 0.18.0-build0
It's fixed now, anyway. -- Downgrade msn-pecan in karmic down to 0.18.0-build0 https://bugs.launchpad.net/bugs/422018 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 422926] Re: MSN chat broken; crashes pidgin
This is fixed in git. Will be available on the next release candidate. ** Changed in: msn-pecan (Ubuntu) Status: New => Fix Committed ** Changed in: msn-pecan (Ubuntu) Assignee: (unassigned) => Felipe Contreras (felipe-contreras) -- MSN chat broken; crashes pidgin https://bugs.launchpad.net/bugs/422926 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 392482] Re: More intuitive way to set personal message
Also, it's one of the most requested features in msn-pecan (an alternative msn plug-in): http://code.google.com/p/msn- pecan/issues/detail?id=51 ** Also affects: hundredpapercuts Importance: Undecided Status: New -- More intuitive way to set personal message https://bugs.launchpad.net/bugs/392482 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 392482] [NEW] More intuitive way to set personal message
Public bug reported: Binary package hint: pidgin The current way to set a personal message is not intuitive: click you status (Available), click you status again, a box opens, type your personal message there. Several alternatives have been proposed, but none accepted by Pidgin developers. There's already a plug-in that improves the situation: http://code.google.com/p/pidgin-personalbar/ I'm an ex-developer so I can write a patch in one day if I knew it was going to be used. ** Affects: hundredpapercuts Importance: Undecided Status: New ** Affects: pidgin (Ubuntu) Importance: Undecided Status: New ** Bug watch added: code.google.com/p/msn-pecan/issues #51 http://code.google.com/p/msn-pecan/issues/detail?id=51 -- More intuitive way to set personal message https://bugs.launchpad.net/bugs/392482 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 324456] Re: pidgin crashed with SIGSEGV in g_hash_table_destroy()
Fixed in msn-pecan 0.0.19. ** Changed in: msn-pecan Importance: Undecided => High ** Changed in: msn-pecan Status: New => Fix Released ** Changed in: msn-pecan Assignee: (unassigned) => Felipe Contreras (felipe-contreras) -- pidgin crashed with SIGSEGV in g_hash_table_destroy() https://bugs.launchpad.net/bugs/324456 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 332091] Re: pidgin crashed with SIGSEGV in msn_message_destroy()
This is fixed in msn-pecan 0.0.19. ** Changed in: msn-pecan Importance: Undecided => High ** Changed in: msn-pecan Status: New => Fix Released ** Changed in: msn-pecan Assignee: (unassigned) => Felipe Contreras (felipe-contreras) -- pidgin crashed with SIGSEGV in msn_message_destroy() https://bugs.launchpad.net/bugs/332091 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 325853] Re: pidgin crashed with SIGSEGV in g_hash_table_destroy()
** Changed in: pidgin (Ubuntu) Assignee: (unassigned) => Felipe Contreras (felipe-contreras) Status: New => Confirmed ** Changed in: msn-pecan (Ubuntu) Sourcepackagename: pidgin => msn-pecan -- pidgin crashed with SIGSEGV in g_hash_table_destroy() https://bugs.launchpad.net/bugs/325853 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 324456] Re: pidgin crashed with SIGSEGV in g_hash_table_destroy()
Thanks for the report. Could you try disabling user displays in the account options. Also, are you using the http method? -- pidgin crashed with SIGSEGV in g_hash_table_destroy() https://bugs.launchpad.net/bugs/324456 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
