Updates:
Cc: [email protected]
Comment #13 on issue 25938 by [email protected]: no proxy settings dialog on
kde
http://code.google.com/p/chromium/issues/detail?id=25938
It would be useful to see the output suggested in comment 10 (with and
without $auto_proxy set, if it
differs), as well as the result from "which kcmshell4" to see if this is
maybe a $PATH problem. Also if
kcmshell4 isn't in /usr/bin or something "normal" like that, it would be
useful to see what the $PATH of
the running chrome process is when started in the normal means (e.g. from
an icon or something) with a
command like:
tr \\000 \\012 < /proc/`pidof google-chrome | tr ' ' \\\\012 | sort | head
-n 1`/environ | grep ^PATH=
I don't see any other obvious reason why we would fail to run "kcmshell4
proxy" from within Chrome
when it runs fine by hand... well unless Chrome doesn't think it's running
in KDE 4 to begin with. But the
output above should clear that up as well, I think.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
