Bug 484570 - Chromium cannot open network settings in Plasma 6
Summary: Chromium cannot open network settings in Plasma 6
Status: RESOLVED DUPLICATE of bug 484444
Alias: None
Product: systemsettings
Classification: Applications
Component: kcmshell (other bugs)
Version First Reported In: 6.0.2
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-03-27 04:34 UTC by Mosklia
Modified: 2024-03-27 23:29 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mosklia 2024-03-27 04:34:50 UTC
***
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

Chromium cannot open network settings in Plasma 6, which can be opened in Plasma 5

STEPS TO REPRODUCE
1. Open Chromium, entering its settings
2. Click System -> Open your computer proxy settings(“打开您计算机的代理设置”)
3. You may see a window saying "无法从 /usr/bin/proxy 加载插件:Failed to extract plugin meta data from '/usr/bin/proxy': '/usr/bin/proxy' is not a Qt plugin (metadata not found)"

OBSERVED RESULT

A window titled "kcmshell6" saying "无法从 /usr/bin/proxy 加载插件:Failed to extract plugin meta data from '/usr/bin/proxy': '/usr/bin/proxy' is not a Qt plugin (metadata not found)"

EXPECTED RESULT

System proxy settings is opened as is worked in Plasma 5.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
ArchLinux 6.8.1-arch1-1 (64 bit)
KDE Plasma Version:  6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION
See https://bbs.archlinux.org/viewtopic.php?id=293966
Comment 1 Mosklia 2024-03-27 04:36:48 UTC
Chromium version: 123.0.6312.58 Arch Linux (64 bit)
Comment 2 Nicolas Fella 2024-03-27 23:29:09 UTC

*** This bug has been marked as a duplicate of bug 484444 ***