Bug 484444

Summary:	Chrome fails to open proxy settings
Product:	[Plasma] plasmashell	Reporter:	0BADC0DE <vincenzo.romano>
Component:	generic-crash	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED UPSTREAM
Severity:	major	CC:	me, nicolas.fella, Sparky_14145
Priority:	NOR
Version First Reported In:	6.0.2
Target Milestone:	1.0
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	Screenshot of the error

Description 0BADC0DE 2024-03-25 11:18:51 UTC

Created attachment 167730 [details]
Screenshot of the error

***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY
KDE/Plasma proxy settings/service not functional:

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)

STEPS TO REPRODUCE
1.  Open a program using system-wide proxy i.e. Google Chrome Browser)
2.  Setup the proxy (i.e. three-dots->settings->system->"Open your computer's proxy settings"

OBSERVED RESULT
A dialog is displayed with the above error message.


EXPECTED RESULT
A window from system-settings is opened to manage proxy settings

SOFTWARE/OS VERSIONS
Kernel Version : 6.8.1.zen1-1
Plasma Version : 6.0.2-3
KDE Version : 24.02.1-1
Frameworks Version : 5.115.0-1
Qt5 Version : 5.15.13+kde+r7-1
Qt6 Version : 6.6.2-4

ADDITIONAL INFORMATION
It used to work with KDE/Plasma 5

Comment 1 Nicolas Fella 2024-03-25 11:39:26 UTC

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

Comment 2 0BADC0DE 2024-03-25 12:31:07 UTC

And what about the fact that is was working correctly until v5?

Comment 3 Nicolas Fella 2024-03-25 13:11:58 UTC

Chrome likely runs different code depending on the Plasma version, and the code for Plasma 6 is broken

Comment 4 Nicolas Fella 2024-03-27 23:29:09 UTC

*** Bug 484570 has been marked as a duplicate of this bug. ***

Comment 5 Aidan Harris 2024-03-29 14:49:45 UTC

(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.