#630 closed System Defect (invalid)

Side-effects of proxy settings

Reported by: beat Owned by:
Priority: major Milestone:
Component: Network Manager Version: 9.1-BETA1
Keywords: proxy Cc: trac-bugs@…

Description

I have to set a proxy with user authentication on my workstation. The proxy settings are done via the PC-BSD Network Manager. Unfortunately this has some side-effects:

  • When starting the warden or a root terminal and check the "Remember password" checkbox a popup shows: "Failed to run xterm as user root. Failed to communicate with gksu-run-helper. Received: basic:*:username:password: No match. While expexting: gksu: waiting"
  • When starting a terminal I've this message: "basic:*:username:password: No match.". I'm using tcsh as shell.

Although setting the proxy settings AppCafe? doesn't work. Deleting the index and restarting pbid doesn't help and the pbid.log only shows the "Started pbid" line.

Change History (1)

comment:1 Changed 21 months ago by kris

  • Resolution set to invalid
  • Status changed from new to closed

I did some testing here and could not duplicate your problem. My guess is that you also changed the hostname at the same time and didn't reboot. Is that the case? That would mess up gksu and others.

The proxy settings only writes the HTTP_PROXY variable to /etc/csh.cshrc and /etc/profile, for csh and sh/bash shells. It takes effect after you logout / login again, or reboot.

I'm going to mark this as fixed, you can re-open it if you can duplicate or confirm that it was something else causing the issue.

Note: See TracTickets for help on using tickets.