https://bugs.kde.org/show_bug.cgi?id=480847
Bug ID: 480847
Summary: Incorrect warning about Chromium proxy settings
Classification: Applications
Product: systemsettings
Version: 5.27.10
Platform: NixOS
OS: Linux
Status: REPORTED
Severity: minor
Priority: NOR
Component: kcm_proxy
Assignee: plasma-b...@kde.org
Reporter: a.eren.bi...@icloud.com
CC: konq-b...@kde.org
Target Milestone: ---
Created attachment 165538
--> https://bugs.kde.org/attachment.cgi?id=165538&action=edit
The mentioned screen.
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
STEPS TO REPRODUCE
1. Open System Settings application
2. Enter Network > Settings > Proxy menu
3. Select "Use manually specified proxy configuration and start typing in the
text input "SOCKS proxy"
OBSERVED RESULT
A warning saying the following appears in the bottom of the application screen.
"Not all applications will use this proxy setting. In particular, Firefox and
Chromium or anything derived from them, or anything using QtWebEngine - which
includes Konqueror using the WebEnginePart, Akregator and Falkon - will not use
these settings. Some applications may allow the proxy to be configured in their
own settings."
But Chromium Version 121.0.6167.85 (Official Build) (64-bit) respects and uses
these proxy settings. This leads to confusion and unnecessary browsing for
Chromium's proxy settings if one doesn't try it beforehand.
This can be seen in Chromium's own docs here:
https://chromium.googlesource.com/chromium/src/+/master/docs/linux/proxy_config.md
> When Chromium detects that it is running in GNOME or KDE, it will
> automatically use the appropriate standard proxy settings.
EXPECTED RESULT
Chromium clause should be removed from this warning, or the specific version
number below which Chromium doesn't use system proxy settings should be
indicated.
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux: Kernel 6.1.75
(available in About System)
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.113.0
Qt Version: 5.15.12
ADDITIONAL INFORMATION
Apparently this was an issue on the Chromium's side in the past (see
https://bugs.kde.org/show_bug.cgi?id=295065) but it is now resolved as can be
seen in the last comment to the bug report I linked.
--
You are receiving this mail because:
You are watching all bug changes.
