OS/Platform: Maemo5 Freemantle SOFTWARE VERSION: 2.2009.51-1.002 EXACT STEPS LEADING TO PROBLEM: (Explain in detail what you do (e.g. tap on OK) and what you see (e.g. message Connection Failed appears)) 1. Connect to a wireless network which requires proxy to connect to the internet 2. add the proxy configuration details to the wireless profile 3. Install the Pidgin Protocols Plugin For Conversations And Contact on the N900 and try to connect to supported IM protocols EXPECTED OUTCOME: Pidgin Protocols Plugin For Conversations And Contact retrives my proxy settings from my wireless profile and uses it to connect or the plugin settings has a gui config which allows me to add my proxy settings. ACTUAL OUTCOME: I am unable to connect to any IM protocol because of the lack of proxy support. REPRODUCIBILITY: always EXTRA SOFTWARE INSTALLED: OTHER COMMENTS: Currently there is no way to get this Pidgin Protocols Plugin For Conversations And Contact on the N900 to work when behind a network proxy. I am not a programmer so forgive my naivety on this, I just felt since this plugin was based on telepathy haze which uses libpuple? same plugin as pidgin. It would be easy to make it work with http proxy. It would be nice if a configuration which would allow the user to input their proxy settings is built into the settings UI of the plugin User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US) AppleWebKit/532.5 (KHTML, like Gecko) Chrome/4.0.249.30 Safari/532.5
Is this plugin still being maintained? I filed bug like over a week ago and I am yet to get a response from the maintainers. Bugzilla is not the easiest of tools to use, and when a user takes his time to report a bug the least thing the developer can do is take a look at the report and get back to the user (fixed, wont fix, pending, incomplete, invalid anything) so the user knows that at least someone listened. I filed the same bug against the msn-pecan plugin (which uses the same library as this plugin) The maintainer not only got back to me, he accepted the bug, tagged it high and got it fixed in less than a week of filling. Am not expecting the same speed from this app but at least acknowledge that my effort was not in vain. Maybe all you guys want to hear is positive feedbacks? In anycase if you dont attend to bug reports perhaps you should take out the "Report a bug against this application. " in the maemo download page so users can safe their time cheer leading
Haze doesn't expose configuring your proxy settings, so without Haze growing support for that, the Maemo 5 UI can't offer these options. Felipe (CCed): how did you support this in your fork of Haze? Did you add account options to Pecan, or expose proxy settings as connection parameters? The vague plan is to make CMs pick up your system proxy settings (probably using libproxy) but given that Maemo doesn't *have* any system proxy settings, maybe we should just expose libpurple's proxy settings as connection parameters for now.
(In reply to comment #2) > Haze doesn't expose configuring your proxy settings, so without Haze growing > support for that, the Maemo 5 UI can't offer these options. Felipe (CCed): how > did you support this in your fork of Haze? Did you add account options to > Pecan, or expose proxy settings as connection parameters? > > The vague plan is to make CMs pick up your system proxy settings (probably > using libproxy) but given that Maemo doesn't *have* any system proxy settings, > maybe we should just expose libpurple's proxy settings as connection parameters > for now. It turns out Maemo does have system proxy settings in a way similar to GNOME: using GConf. In telepathy-msn-pecan I hacked the internal libpurple so that it assumes we are in a GNOME environment (the current checks return 'false'). Then libpurple goes on fetching the proxy settings using system calls to gconftool-2 (ugly!) and everything works fine.
I forgot to mention. I have partial patches for telepathy-haze to use GConf to fetch the proxy settings and setup libpurple properly (without modifications inside libpurple). However, I decided against that approach once I found out the aforementioned hack which is much simpler.
Do you have your partial patches kicking around as a starting point? I think that's probably a good approach.
Created attachment 33202 [details] [review] Partial GConf support Here's the patch. You would have to change my Makefile stuff for the autotools equivalent :)
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-haze/issues/29.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.