Proxy with Kde Plasma

ARM
1

My proxy in the system setting doesn’t work as it should be. After setting it up, it doesn’t redirect any network to the proxy I filled in. So I have been use the network setting of firefox all the time. But I am playing with retroarch recently, which can’t download anything without proxy. Help me please…:smiling_face_with_tear::smiling_face_with_tear::smiling_face_with_tear:

2

Hi @alexCa,

Without knowing how you set up the proxy, there’s very little we can do to help. Please provide a better, more clearer question. Please see:

Please also note and heed: Forum Rules - Manjaro

Those with privacy concerns: note that when -z, or --filter is used, all personally identifiable information is filtered out from the resulting inxi output. :eyes:

This is a vast subject, as evident by:

https://wiki.archlinux.org/title/Proxy_server

So we’d need a lot more information.

3

Sorry for the problem I caused. Here is the clearer question and output:
I can’t set up system proxy.

System:
  Kernel: 6.12.19-1-MANJARO-RPI4 arch: aarch64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: arch_sys_counter parameters: reboot=w coherent_pool=1M
    8250.nr_uarts=1 pci=pcie_bus_safe cgroup_disable=memory
    numa_policy=interleave smsc95xx.macaddr=2C:CF:67:A8:6C:44
    vc_mem.mem_base=0x3fc00000 vc_mem.mem_size=0x40000000
    root=PARTUUID=aa7fddd0-02 rw rootwait console=ttyAMA10,115200 console=tty3
    selinux=0 quiet splash plymouth.ignore-serial-consoles
    smsc95xx.turbo_mode=N dwc_otg.lpm_enable=0 usbhid.mousepoll=8 audit=0
  Desktop: KDE Plasma v: 6.3.3 tk: Qt v: N/A info: frameworks v: 6.11.0
    wm: kwin_wayland vt: 1 dm: SDDM Distro: Manjaro ARM base: Arch Linux
Machine:
  Type: ARM System: Raspberry Pi 5 Model B Rev 1.1 details: N/A rev: d04171
    serial: <filter>
Battery:
  Device-1: hidpp_battery_0 model: Logitech G304 Lightspeed Wireless Gaming
    Mouse serial: <filter> charge: 100% (should be ignored) rechargeable: yes
    status: discharging
Memory:
  System RAM: total: N/A available: 7.75 GiB used: 3.28 GiB (42.4%) igpu: 8 MiB
  RAM Report: message: No RAM data found using udevadm.
PCI Slots:
  Message: No ARM data found for this feature.
CPU:
  Info: model: N/A variant: cortex-a76 bits: 64 type: MCP arch: ARMv8 family: 8
    model-id: 4 stepping: 1
  Topology: cpus: 1x clusters: 1 cores: 4 smt: <unsupported> cache:
    L1: 512 KiB desc: d-4x64 KiB; i-4x64 KiB L2: 2 MiB desc: 4x512 KiB L3: 2 MiB
    desc: 1x2 MiB
  Speed (MHz): avg: 1600 min/max: 1500/2400 scaling: driver: cpufreq-dt
    governor: ondemand cores: 1: 1600 2: 1600 3: 1600 4: 1600 bogomips: 432
  Features: aes asimd asimddp asimdhp asimdrdm atomics cpuid crc32 dcpop
    evtstrm fp fphp lrcpc pmull sha1 sha2
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: __user pointer sanitization
  Type: spectre_v2 mitigation: CSV2, BHB
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: bcm2712-hdmi0 driver: vc4_hdmi v: N/A bus-ID: N/A
    chip-ID: brcm:107c701400 class-ID: hdmi
  Device-2: bcm2712-hdmi1 driver: vc4_hdmi v: N/A bus-ID: N/A
    chip-ID: brcm:107c706400 class-ID: hdmi
  Display: wayland server: X.org v: 1.21.1.16 with: Xwayland v: 24.1.6
    compositor: kwin_wayland driver: X: loaded: modesetting alternate: fbdev
    dri: vc4
    gpu: vc4-drm,vc4_crtc,vc4_dpi,vc4_dsi,vc4_firmware_kms,vc4_hdmi,vc4_hvs,vc4_txp,vc4_v3d,vc4_vec
    display-ID: 0
  Monitor-1: HDMI-A-1 model: FKS-C215J serial: <filter> built: 2022 res:
    mode: 1920x1080 hz: 60 scale: 100% (1) dpi: 102 gamma: 1.2 chroma: red:
    x: 0.647 y: 0.345 green: x: 0.322 y: 0.631 blue: x: 0.153 y: 0.059 white:
    x: 0.314 y: 0.329 size: 476x268mm (18.74x10.55") diag: 546mm (21.5")
    ratio: 16:9 modes: 1920x1080, 1920x1080i, 1680x1050, 1280x1024, 1440x900,
    1280x960, 1280x800, 1152x864, 1280x720, 1440x576, 1024x768, 1440x480,
    832x624, 800x600, 720x576, 720x576i, 720x480, 720x480i, 640x480, 720x400
  API: EGL v: 1.5 hw: drv: broadcom v3d platforms: device: 0 drv: v3d
    device: 1 drv: swrast gbm: drv: v3d surfaceless: drv: v3d wayland: drv: v3d
    x11: drv: v3d
  API: OpenGL v: 4.5 compat-v: 3.1 vendor: broadcom mesa v: 25.0.1-arch1.2
    glx-v: 1.4 direct-render: yes renderer: V3D 7.1.10.2 device-ID: 14e4:ffffffff
    memory: 7.56 GiB unified: yes display-ID: :1.0
  API: Vulkan Message: No Vulkan data available.
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor wl: wayland-info
    x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: bcm2712-hdmi0 driver: vc4_hdmi bus-ID: N/A chip-ID: brcm:107c701400
    class-ID: hdmi
  Device-2: bcm2712-hdmi1 driver: vc4_hdmi bus-ID: N/A
    chip-ID: brcm:107c706400 class-ID: hdmi
  API: ALSA v: k6.12.19-1-MANJARO-RPI4 status: kernel-api
    tools: alsactl,alsamixer,amixer
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 1.4.0 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Raspberry Pi RP1 PCIe 2.0 South Bridge driver: rp1 v: kernel pcie:
    gen: 2 speed: 5 GT/s lanes: 4 port: N/A bus-ID: 01:00.0 chip-ID: 1de4:0001
    class-ID: 0200
  IF: wlan0 state: up mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: noprefixroute scope: link
  IF-ID-1: end0 state: down mac: <filter>
  Info: services: NetworkManager, sshd, systemd-networkd, systemd-timesyncd,
    wpa_supplicant
  WAN IP: <filter>
Bluetooth:
  Device-1: bcm7271-uart driver: bcm7271_uart bus-ID: N/A
    chip-ID: brcm:107d50c000 class-ID: serial
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 118.04 GiB used: 22.73 GiB (19.3%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/mmcblk0 maj-min: 179:0 vendor: SanDisk model: SD64G
    size: 59.45 GiB block-size: physical: 512 B logical: 512 B type: Removable
    tech: SSD serial: <filter> scheme: MBR
  ID-2: /dev/sda maj-min: 8:0 vendor: Lenovo model: 64GB thinkplus
    size: 58.59 GiB block-size: physical: 512 B logical: 512 B type: USB rev: 3.1
    spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: N/A serial: <filter>
    fw-rev: 3.00 scheme: MBR
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 58.97 GiB size: 57.98 GiB (98.32%) used: 22.66 GiB (39.1%)
    fs: ext4 dev: /dev/mmcblk0p2 maj-min: 179:2 label: ROOT_MNJRO
    uuid: d0365520-aedf-4d98-a77b-350122736c3f
  ID-2: /boot raw-size: 457.8 MiB size: 457.5 MiB (99.94%)
    used: 75.8 MiB (16.6%) fs: vfat dev: /dev/mmcblk0p1 maj-min: 179:1
    label: BOOT_MNJRO uuid: 14E9-C189
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 80 (default 100) zswap: no
  ID-1: swap-1 type: zram size: 11.62 GiB used: 0 KiB (0.0%) priority: 100
    comp: zstd avail: lzo-rle,lzo,lz4 max-streams: 4 dev: /dev/zram0
Unmounted:
  ID-1: /dev/sda1 maj-min: 8:1 size: 58.59 GiB fs: exfat label: Anon
    uuid: EFDF-F6E4
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 2 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Device-1: 1-2:2 info: Logitech USB Receiver type: keyboard,mouse,HID
    driver: logitech-djreceiver,usbhid interfaces: 3 rev: 2.0
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 98mA
    chip-ID: 046d:c53f class-ID: 0300
  Hub-2: 2-0:1 info: super-speed hub ports: 1 rev: 3.0
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Device-1: 2-1:2 info: Lenovo 64GB thinkplus type: mass storage
    driver: usb-storage interfaces: 1 rev: 3.1 speed: 5 Gb/s (596.0 MiB/s)
    lanes: 1 mode: 3.2 gen-1x1 power: 144mA chip-ID: 346d:5678 class-ID: 0806
    serial: <filter>
  Hub-3: 3-0:1 info: hi-speed hub with single TT ports: 2 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Device-1: 3-2:2 info: Telink VXE V87 2.4G Dongle type: keyboard
    driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 200mA chip-ID: 320f:5088 class-ID: 0301
  Hub-4: 4-0:1 info: super-speed hub ports: 1 rev: 3.0
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 1d6b:0003
    class-ID: 0900
Sensors:
  System Temperatures: cpu: 56.6 C mobo: N/A
  Fan Speeds (rpm): cpu: 2375
Repos:
  Packages: pm: pacman pkgs: 1081 libs: 257 tools: pamac,yay
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: https://mirrors.jlu.edu.cn/manjaro/arm-unstable/$repo/$arch
    2: https://mirrors.tuna.tsinghua.edu.cn/manjaro/arm-unstable/$repo/$arch
    3: https://mirror.raiolanetworks.com/manjaro/arm-unstable/$repo/$arch
    4: https://mirror.netcologne.de/manjaro/arm-unstable/$repo/$arch
    5: https://mirror.archlinux.tw/Manjaro/arm-unstable/$repo/$arch
    6: https://mirror.phoepsilonix.love/manjaro/arm-unstable/$repo/$arch
    7: https://mirror.vinehost.net/manjaro/arm-unstable/$repo/$arch
    8: https://mirrors.sonic.net/manjaro/arm-unstable/$repo/$arch
    9: https://mirror.math.princeton.edu/pub/manjaro/arm-unstable/$repo/$arch
    10: https://mirrors.ocf.berkeley.edu/manjaro/arm-unstable/$repo/$arch
    11: https://mirror.hostiko.network/manjaro/arm-unstable/$repo/$arch
    12: https://www.mirrorservice.org/sites/repo.manjaro.org/repos/arm-unstable/$repo/$arch
    13: https://mirror.leitecastro.com/manjaro/arm-unstable/$repo/$arch
    14: https://mirror.freedif.org/Manjaro/arm-unstable/$repo/$arch
    15: https://mirror.alpix.eu/manjaro/arm-unstable/$repo/$arch
    16: https://repo.ialab.dsu.edu/manjaro/arm-unstable/$repo/$arch
    17: https://mirror.2degrees.nz/manjaro/arm-unstable/$repo/$arch
    18: https://mirrors.cicku.me/manjaro/arm-unstable/$repo/$arch
    19: https://manjaro.mirrors.lavatech.top/arm-unstable/$repo/$arch
    20: https://mirror.dkm.cz/manjaro/arm-unstable/$repo/$arch
    21: https://manjaro.kurdy.org/arm-unstable/$repo/$arch
    22: https://ftp.gwdg.de/pub/linux/manjaro/arm-unstable/$repo/$arch
    23: https://manjaro.ipacct.com/manjaro/arm-unstable/$repo/$arch
    24: https://muug.ca/mirror/manjaro/arm-unstable/$repo/$arch
    25: https://mirrors.eric.ovh/manjaro/arm-unstable/$repo/$arch
    26: https://mirror.koddos.net/manjaro/arm-unstable/$repo/$arch
    27: https://manjaro.c3sl.ufpr.br/arm-unstable/$repo/$arch
    28: https://mirrors.gigenet.com/manjaro/arm-unstable/$repo/$arch
    29: https://mirrors.atlas.net.co/manjaro/arm-unstable/$repo/$arch
    30: https://mirror.easyname.at/manjaro/arm-unstable/$repo/$arch
    31: https://bd.mirror.vanehost.com/Manjaro/arm-unstable/$repo/$arch
    32: https://ftp.lysator.liu.se/pub/manjaro/arm-unstable/$repo/$arch
    33: https://mirror.truenetwork.ru/manjaro/arm-unstable/$repo/$arch
    34: https://ftp.caliu.cat/pub/distribucions/manjaro/arm-unstable/$repo/$arch
    35: https://manjarolinux-mirror.cloud.mu/arm-unstable/$repo/$arch
    36: https://ftpmirror1.infania.net/mirror/manjaro/arm-unstable/$repo/$arch
    37: https://mirror.xenyth.net/manjaro/arm-unstable/$repo/$arch
    38: https://mirror.23m.com/manjaro/arm-unstable/$repo/$arch
    39: https://mirror.ufro.cl/manjaro/arm-unstable/$repo/$arch
    40: https://mirrors.nic.cz/manjaro/arm-unstable/$repo/$arch
    41: https://mirror.kamtv.ru/manjaro/arm-unstable/$repo/$arch
    42: https://mirror.init7.net/manjaro/arm-unstable/$repo/$arch
    43: https://manjaro.mirror.liquidtelecom.com/arm-unstable/$repo/$arch
    44: https://mirror.futureweb.be/manjaro/arm-unstable/$repo/$arch
    45: https://mirrors2.manjaro.org/arm-unstable/$repo/$arch
    46: https://manjaro.mirror.wearetriple.com/arm-unstable/$repo/$arch
    47: https://manjaro.ynh.ovh/arm-unstable/$repo/$arch
    48: https://mirror.telepoint.bg/manjaro/arm-unstable/$repo/$arch
    49: https://mirrors.manjaro.org/repo/arm-unstable/$repo/$arch
    50: https://ftp.halifax.rwth-aachen.de/manjaro/arm-unstable/$repo/$arch
    51: https://mirror.bouwhuis.network/manjaro/arm-unstable/$repo/$arch
    52: https://mirror.zetup.net/manjaro/arm-unstable/$repo/$arch
    53: https://mirror.yandex.ru/mirrors/manjaro/arm-unstable/$repo/$arch
Processes:
  CPU top: 5 of 232
  1: cpu: 25.6% command: firefox pid: 4401 mem: 659.4 MiB (8.3%)
  2: cpu: 16.6% command: firefox pid: 4499 mem: 75.3 MiB (0.9%)
  3: cpu: 13.9% command: firefox pid: 10054 mem: 433.8 MiB (5.4%)
  4: cpu: 9.4% command: konsole pid: 15843 mem: 128.1 MiB (1.6%)
  5: cpu: 8.2% command: firefox pid: 14221 mem: 241.9 MiB (3.0%)
  Memory top: 5 of 232
  1: mem: 659.4 MiB (8.3%) command: firefox pid: 4401 cpu: 25.6%
  2: mem: 433.8 MiB (5.4%) command: firefox pid: 10054 cpu: 13.9%
  3: mem: 425.6 MiB (5.3%) command: plasmashell pid: 912 cpu: 1.1%
  4: mem: 293.3 MiB (3.6%) command: firefox pid: 9830 cpu: 5.1%
  5: mem: 241.9 MiB (3.0%) command: firefox pid: 14221 cpu: 8.2%
Info:
  Processes: 232 Power: uptime: 1h 22m suspend: services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
    tool: systemctl
  Compilers: clang: 19.1.7 gcc: 14.2.1 Shell: Bash v: 5.2.37
    running-in: konsole inxi: 3.3.37
4

Setting a proxy via Plasma’s System Settings will only affect KDE apps, as they use KIO. Pretty much everything else accessing the network will use your system’s network settings.

Most major browsers (such as Firefox) offer the choice between using the system’s proxy settings or manual proxy configuration:

5

Are there TWO system network settings? But I can’t find the other system’s network settings🥲

6

You can access the system network settings via Plasma’s System Settings as there is some integration with the Network Manager which allows the settings to be easily accessed. The option is “Wi-Fi & Networking”, which is immediately above the “Proxy” option. It can also be accessed by right-clicking on the NetworkManager icon in your system tray & selecting “Configure Network Connections”.

However, I don’t know how you actually go about adding a proxy to be used as default by the entire system - you might have to do some reading at the link provided earlier:

1 Like
7

Maybe this helps:

https://unix.stackexchange.com/a/213777

(It shouldn’t be copied and pasted obviously. It should be adapted for you.)

8

Thank you! The “WiFi & Networking” doesn’t have any setting to proxy tho. But I will keep searching, thank you for help!! :kissing_heart::kissing_heart:

9

Thank you! I will give it a try!

1 Like
10

That’s why I suggested you read the link. Adding a proxy might involve installing a package that will then enable you to select the proxy in the network settings. It might even appear in the same drop-down menu as the VPN option (after all, a VPN is a type of proxy).

11

OK! I will try that page out! Thank U!! :kissing_heart::kissing_heart::kissing_heart:

12

Check here:

https://i.imgur.com/44kcEAT.png

Edit:

From Coding Mantis :

Setting up proxy inside the terminal

If you are not using a system wide proxy then you also need to setup proxy for all the connections that you might make from inside of your terminal. This was easy I only needed to add a couple of environment variables into my .bashrc to make it work. The changes were as follows-

CONTENT FOR PROXY

export http_proxy=http://proxy.iiit.ac.in:8080/
export https_proxy=$http_proxy export ftp_proxy=$http_proxy
export rsync_proxy=$http_proxy export ssh_proxy=$http_proxy
export no_proxy="localhost, 127.0.0.1, *iiit.ac.in, *iiit.net, 172.16.*.*, 172.17.*.*, 192.168.*.*, 10.*.*.*"

You might need to replace the value of variables by your own proxy URL.

Setting up proxy for sudo

The above changes will allow you to define proxy for all commands that you execute with user-level priveleges. But, if you try to execute any program which requires you to use root access or sudo(substitute user do) then you won’t be able to. For this you need to add an additional line to your sudoers file.

Please edit the sudoers file using sudo visudo command only!

Inside the sudoers file I only had to add an additional line to modify the defualt env_variables so that it also includes $http_proxy

Defaults env_keep += "https_proxy http_proxy"
2 Likes
13

That’s what I mentioned earlier - apparently that option only affects KDE apps which use KIO.

Although the 2 Reddit threads I got that info from are a few years old:

https://www.reddit.com/r/kde/comments/10u8j5s/why_does_the_proxy_setting_on_kde_plasma_not_work/

https://www.reddit.com/r/kde/comments/lnd4j8/does_proxy_work_in_kde/

Things may have changed with Plasma 6.

The 2nd Reddit thread does have one solution that worked, however that was 4 years ago:

denisfalqueto

• 4y ago

Unfortunately, proxy configuration in Linux in general is very finicky. That configuration on System Settings is obeyed only by KDE applications. So, for other apps, you’ll have to configure them separately.

What I did was a two-fold solution:

  • install and configure cntlm, for a local proxy service. You may need another service, depending on your proxy’s authentication method. Cntlm is used because at my job, they use a Windows AD for authentication.
  • Configure environment variables http_proxy and https_proxy to http://localhost:3128 (port may change, depending on your specific local proxy).
  • Configure each application to use $http_proxy or $https_proxy, accordingly.

As I said, each application will have to be configured in its own way.

14

This is exactly what i have done. That setting doesn’t do anything.

Oh! I am about to try the export thing. I am reading the pages to look for how to change it. Thank you guys!

2 Likes
16

@Mirdarthos @scotty65
Good news! The export command works!
Bad news! It doesn’t affect the ping command, is there anything I can do with?
Also, does write those command in ~/.bashrc means I have to open the terminal once, before I can reach the internet?
Not big problem tho, I have to use terminal to start up proxy anyway. Just to make sure I write those command in the right place.
Thank you guys so much. I love you guys, best community ever :kissing_heart::kissing_heart::kissing_heart:

2 Likes
17

Because only when you open the terminal emulator that file gets executed. If you used ZSH it would’ve been ~/.zshrc. It can be changed, though. But you said it’s not a problem, so I’m guessing it’s not a problem.

That I do not have the foggiest idea about, but my logic says no. Because it checks direct connectivity, and by it’s very nature there’s no direct connectivity through a proxy.

1 Like
18

Oh!! Then that’s should be fine! Thank you!!!

1 Like
19

Ok, I found something easy and helpful. Some proxy front end has “TUN Mode”, I guess it create a virtual network adapter which make the whole computer network go through it, end up a TRUE “system wide” proxy.

1 Like