https://bugs.kde.org/show_bug.cgi?id=48
Aidan Harris changed:
What|Removed |Added
CC||m...@aidanharr.is
--- Comment #5 from Aidan Harris ---
(In reply to Nicolas Fella from comment #1)
> This looks like Chrome is invoking the proxy settings incorrectly.
>
> It looks like it is running "kcmshell6 /usr/bin/proxy", which makes no
> sense. It should be "kcmshell6 kcm_proxy", or better something like
> "xdg-open systemsettings://kcm_proxy".
>
> Please report this to Chrome
I can reproduce this but it works on a checked out build of kcmutils. Any idea
why it works differently? Why would kcmutils work differently when installed
compared to when ran in-tree?
$ kcmshell6 proxy
kf.coreaddons: "Could not load plugin from /usr/bin/proxy: Failed to extract
plugin meta data from '/usr/bin/proxy': '/usr/bin/proxy' is not a Qt plugin
(metadata not found)"
kf.coreaddons: "Could not load plugin from /usr/bin/proxy: Failed to extract
plugin meta data from '/usr/bin/proxy': '/usr/bin/proxy' is not a Qt plugin
(metadata not found)"
git clone https://invent.kde.org/frameworks/kcmutils.git kcmutils
cd kcmutils
mkdir build
cd build
cmake ..
make -j$(nproc)
cd -
env PATH="${PWD}/build/bin:${PATH}" ./build/bin/kcmshell6 proxy
# displays the proxy dialogue as expected.
--
You are receiving this mail because:
You are watching all bug changes.
