[Jaunty] Pidgin reports "Proxy configuration program was not found."

Bug #331067 reported by Rebecca Menessec
26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
pidgin (Fedora)
Fix Released
Medium
pidgin (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Binary package hint: pidgin

I'm trying to get Pidgin to connect to a locally forwarding ssh tunnel to another host to use an http proxy (Apache 2.2.11). I do *not* want to use global GNOME prefs for this-- the tunnel is for Pidgin's use only.

Problem has been ongoing since I installed Jaunty about a week and a half ago. I've been installing all upgrades at least twice daily, and I still can't define a proxy for Pidgin.

Revision history for this message
LinkinXp (linkinxp) wrote :

I have the same problem running Jaunty kernel 2.6.28-8-generic and Pidgin 2.5.4

:)

Changed in pidgin:
status: New → Confirmed
Revision history for this message
LinkinXp (linkinxp) wrote : Re: [Bug 331067] Re: [Jaunty] Pidgin reports "Proxy configuration program was not found."

I have the same problem... but im using Tsocks to achieve the same
result...luck

On Sat, Mar 21, 2009 at 5:53 AM, Surfaz Gemon Meme <email address hidden>wrote:

> ** Changed in: pidgin (Ubuntu)
> Status: New => Confirmed
>
> --
> [Jaunty] Pidgin reports "Proxy configuration program was not found."
> https://bugs.launchpad.net/bugs/331067
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “pidgin” source package in Ubuntu: Confirmed
>
> Bug description:
> Binary package hint: pidgin
>
> I'm trying to get Pidgin to connect to a locally forwarding ssh tunnel to
> another host to use an http proxy (Apache 2.2.11). I do *not* want to use
> global GNOME prefs for this-- the tunnel is for Pidgin's use only.
>
> Problem has been ongoing since I installed Jaunty about a week and a half
> ago. I've been installing all upgrades at least twice daily, and I still
> can't define a proxy for Pidgin.
>

--
Jorge Suarez
---------------------------
Certified
CompTIA
Network+
A+

Revision history for this message
darkharmonics (pimptastic1) wrote :

This feature is required to make simpserver work with pidgin. I can confirm that the latest version 2.5.6 from the pidgin PPA still has this issue.

Revision history for this message
Bogdan Harjoc (harjoc-gmail) wrote :

What's worse, the GNOME version from Jaunty doesn't have gnome-network-preferences anymore (the "proxy configuration program"). It's now called gnome-network-properties.

Making a symlink is enough if you want to change the global settings from pidgin.

If you want the old proxy settings dialog, you'll have to convinge pidgin it's not running under gnome:

GNOME_DESKTOP_SESSION_ID= pidgin

Revision history for this message
In , Felix (felix-redhat-bugs) wrote :

Description of problem:
When I go to Tools - Preferences - Network, pidgin tells me that the proxy configuration program was not found. Therefore the button to configure proxies system-wide is disabled.

Version-Release number of selected component (if applicable):
pidgin-2.5.8-1.fc11.x86_64

How reproducible:
Always

Actual results:
- Button is disabled, notification text is displayed

Expected results:
- Button should be clickable

Additional info:
The problem is that pidgin checks for gnome-network-preferences but in Fedora 11 it is called gnome-network-properties. As a workaround I can just create a symlink in /usr/bin and the button starts working.

Revision history for this message
In , Elliott (elliott-redhat-bugs) wrote :
Revision history for this message
In , Mark (mark-redhat-bugs) wrote :
Revision history for this message
Mark Doliner (thekingant) wrote :

FYI this bug was fixed upstream by Elliott 'QuLogic' Sales de Andrade: http://developer.pidgin.im/viewmtn/revision/info/79639d895e39ef23c24691d0736a265373e2b49c

The fix was included in Pidgin 2.6.4, which was released on 29 November 2009.

Revision history for this message
Rebecca Menessec (aloishammer-deactivatedaccount) wrote :

Mark: Nice to know they put such a rush on it. :D

I'd frankly be using something else by this point (any time post-2.2 or so) if anything else looked halfway viable and/or didn't have KDE dependencies (Qt, I don't mind). ...and also supported OTR.

So, I suppose my problem's been fixed for the last couple months via ~frasten's PPA. I'll keep that in mind for the next time I have a job that mindlessly blocks all IM nets and I have to tunnel home to get from point A to point B via point C.

Revision history for this message
Victor Vargas (kamus) wrote :

Accordding to the last message this issue is solved in latest releases, marked as fixed released then. Thanks!

Changed in pidgin (Ubuntu):
importance: Undecided → Low
status: Confirmed → Fix Released
Changed in pidgin (Fedora):
importance: Unknown → Medium
status: Unknown → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.