Garuda Network Assistant won't open

I must say that because it looks like those two hooked echother. When friend who installed me this get up this morning he'll text me which exact garuda this is.

Please edit your posts.

Wayfire???

I'm sorry, but why does a core component that is installed in Garuda by default not exist?

Edit: because Wayfire and Lxqt editions don't use it. :grimacing:

3 Likes

Nope. Not his fault.

Sorry, we most definitely don't provide 3rd party support. Your friend installed it? Let your friend support it.

3 Likes

It seems so.

How does network and NM work on wayfire?

1 Like

Wayfire + sway + lxqt use

Connman + iwd for networking

To connect to wifi

You can use connman-gtk

app on wayfire and sway

For lxqt you can use
cmst

6 Likes

Hi, I have the same issue and a very similar error message, even though it seems like me and OP don't share the DE (I'm on Sway).

My error message:

Authorization required, but no authorization protocol specified
qt.qpa.xcb: could not connect to display :0
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.

fish: Job 1, 'sudo garuda-network-assistant' terminated by signal SIGABRT (Abort)

I also tried setting QT_QPA_PLATFORM to either xcb or wayland;xcb but it didn't help.

The output of inxi is:

System:    Kernel: 5.12.6-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 11.1.0
           parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen root=UUID=db25428f-ec7d-4092-977e-4c13c814b3d3 rw
           [email protected] quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
           systemd.unified_cgroup_hierarchy=1 loglevel=3
           Desktop: sway 1.6 vt: 1 dm: N/A Distro: Garuda Linux base: Arch Linux
Machine:   Type: Laptop System: Dell product: XPS 13 9343 v: N/A serial: <filter> Chassis: type: 9 serial: <filter>
           Mobo: Dell model: 0TM99H v: A00 serial: <filter> UEFI: Dell v: A15 date: 01/23/2018
Battery:   ID-1: BAT0 charge: 1.9 Wh (100.0%) condition: 1.9/52.7 Wh (3.7%) volts: 8.4 min: 7.6 model: SMP DELL RWT1R43
           type: Li-poly serial: <filter> status: Full
CPU:       Info: Dual Core model: Intel Core i5-5200U bits: 64 type: MT MCP arch: Broadwell family: 6 model-id: 3D (61)
           stepping: 4 microcode: 2F cache: L2: 3 MiB
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 17559
           Speed: 2195 MHz min/max: 500/2700 MHz Core speeds (MHz): 1: 2195 2: 2196 3: 2195 4: 2195
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled
           Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
           Type: mds mitigation: Clear CPU buffers; SMT vulnerable
           Type: meltdown mitigation: PTI
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
           Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling
           Type: srbds mitigation: Microcode
           Type: tsx_async_abort status: Not affected
Graphics:  Device-1: Intel HD Graphics 5500 vendor: Dell driver: i915 v: kernel bus-ID: 00:02.0 chip-ID: 8086:1616
           class-ID: 0300
           Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 2-5:4 chip-ID: 0bda:5682 class-ID: 0e02
           serial: <filter>
           Display: wayland server: X.Org 1.21.1.1 compositor: sway v: 1.6 driver: loaded: i915
           note: n/a (using device driver) display-ID: :0 screens: 1
           Screen-1: 0 s-res: 1920x2160 s-dpi: 96 s-size: 508x572mm (20.0x22.5") s-diag: 765mm (30.1")
           OpenGL: renderer: Mesa Intel HD Graphics 5500 (BDW GT2) v: 4.6 Mesa 21.1.1 direct render: Yes
Audio:     Device-1: Intel Broadwell-U Audio vendor: Dell driver: snd_hda_intel v: kernel bus-ID: 00:03.0 chip-ID: 8086:160c
           class-ID: 0403
           Device-2: Intel Wildcat Point-LP High Definition Audio vendor: Dell driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
           chip-ID: 8086:9ca0 class-ID: 0403
           Sound Server-1: ALSA v: k5.12.6-zen1-1-zen running: yes
           Sound Server-2: sndio v: N/A running: no
           Sound Server-3: JACK v: 0.125.0 running: no
           Sound Server-4: PulseAudio v: 14.2 running: no
           Sound Server-5: PipeWire v: 0.3.28 running: yes
Network:   Device-1: Broadcom BCM4352 802.11ac Wireless Network Adapter vendor: Dell driver: wl v: kernel modules: bcma
           port: f040 bus-ID: 02:00.0 chip-ID: 14e4:43b1 class-ID: 0280
           IF: wlan0 state: up mac: <filter>
           Device-2: Realtek RTL8152 Fast Ethernet Adapter type: USB driver: r8152 bus-ID: 2-1:5 chip-ID: 0bda:8152
           class-ID: 0000 serial: <filter>
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
Bluetooth: Device-1: Broadcom BCM20702A0 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 2-3:3 chip-ID: 0a5c:216f
           class-ID: fe01 serial: <filter>
           Report: bt-adapter ID: hci0 rfk-id: 2 state: up address: <filter>
Drives:    Local Storage: total: 119.24 GiB used: 17.67 GiB (14.8%)
           SMART Message: Required tool smartctl not installed. Check --recommends
           ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD PM851 M.2 2280 128GB size: 119.24 GiB block-size:
           physical: 512 B logical: 512 B speed: 6.0 Gb/s rotation: SSD serial: <filter> rev: 5D0Q scheme: GPT
Partition: ID-1: / raw-size: 118.99 GiB size: 118.99 GiB (100.00%) used: 17.67 GiB (14.9%) fs: btrfs dev: /dev/sda2
           maj-min: 8:2
           ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 546 KiB (0.2%) fs: vfat dev: /dev/sda1 maj-min: 8:1
           ID-3: /home raw-size: 118.99 GiB size: 118.99 GiB (100.00%) used: 17.67 GiB (14.9%) fs: btrfs dev: /dev/sda2
           maj-min: 8:2
           ID-4: /var/log raw-size: 118.99 GiB size: 118.99 GiB (100.00%) used: 17.67 GiB (14.9%) fs: btrfs dev: /dev/sda2
           maj-min: 8:2
           ID-5: /var/tmp raw-size: 118.99 GiB size: 118.99 GiB (100.00%) used: 17.67 GiB (14.9%) fs: btrfs dev: /dev/sda2
           maj-min: 8:2
Swap:      Kernel: swappiness: 10 (default 60) cache-pressure: 75 (default 100)
           ID-1: swap-1 type: zram size: 1.92 GiB used: 83.8 MiB (4.3%) priority: 32767 dev: /dev/zram0
           ID-2: swap-2 type: zram size: 1.92 GiB used: 81.3 MiB (4.1%) priority: 32767 dev: /dev/zram1
           ID-3: swap-3 type: zram size: 1.92 GiB used: 80.9 MiB (4.1%) priority: 32767 dev: /dev/zram2
           ID-4: swap-4 type: zram size: 1.92 GiB used: 83.3 MiB (4.2%) priority: 32767 dev: /dev/zram3
Sensors:   System Temperatures: cpu: 63.0 C mobo: 45.0 C sodimm: SODIMM C
           Fan Speeds (RPM): cpu: 0
Info:      Processes: 265 Uptime: 2d 42m wakeups: 5 Memory: 7.67 GiB used: 4.44 GiB (57.8%) Init: systemd v: 248
           tool: systemctl Compilers: gcc: 11.1.0 clang: 11.1.0 Packages: pacman: 1293 lib: 323 Shell: fish v: 3.2.2
           running-in: alacritty inxi: 3.3.04

Not sure how related that is, but I also had some WiFi issues - it sometimes disconnects and I can't get it to detect any network. It usually resolves itself after some time. I did see an advice to stop MAC address randomization, so I followed it and we'll see if it helps.

Why are you running it with sudo ?

Umm, when I don't I see a pop up window telling me that you must run this program as root, so I do.

Other Garuda settings software doesn't require me to, though.

Right, but why did you run it with sudo in the first place? Did you just think "oh, here's a command, I'll run it with sudo and see what it does to my system" ? Or was there an actual reason for it?

Did you try it without sudo?

I definitely remember that a few days ago, shortly after installing Garuda, I was able to open the GNA from both the GUI launcher and the terminal, and I believe that when I did that I didn't use sudo. I've been using Linux for a few years now, so I definitely try to minimize sudos whenever I can.

I didn't change anything with respect to my network stack before WiFi and GNA started failing, and since then I only changed that single MAC address randomization line in /etc.

And what happens when you try to open if from a terminal now (without sudo)?

I already answered that above - I said that a pop up window tells me that garuda-network-assistant can only be run as root.

1 Like

Argh. I missed the second "I" so I read it as "when I don't see a pop up window", hence my initial confusion as to why you would run a command with sudo for no apparent reason, whereas there is a clear reason for it. OK.

Can you try running it with

pkexec env DISPLAY=$DISPLAY XAUTHORITY="$HOME/.Xauthority" garuda-network-assistant

?

1 Like

It did ask me for sudo permissions and after entering my password it gave me the same error:

Authorization required, but no authorization protocol specified
qt.qpa.xcb: could not connect to display :0
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.

fish: Job 1, 'pkexec env DISPLAY=$DISPLAY XAU…' terminated by signal SIGABRT (Abort)
1 Like

OK, so I reckon this is most likely related to Wayland.

Which Wayland-related packages do you have installed? e.g. is qt5-wayland installed?

1 Like

Yup. Reinstalling it with sudo pacman -S qt5-wayland didn't solve the issue.

 ╭─[email protected] in ~
 ╰─λ pacman -Q | rg wayland                                                                                   (base)
bemenu-wayland 0.5.0-4
lib32-wayland 1.19.0-1
qt5-wayland 5.15.2+kde+r23-1
wayland 1.19.0-1
wayland-protocols 1.21-1
xorg-xwayland 21.1.1-1

A quick update - I managed to open connman-gtk, which I guess is a subset of the network assistant? Anyways, what I did was to run it without the tray icon: connman-gtk --no-icon, as the tray icon seems to have a Wayland-related bug. In the connman-gtk settings I made sure that it doesn't open to the tray only, and now I can run it without the flag.

The GNA is still not working though, and I believe that my WiFi issues will persist even after I fixed the GTK frontend, but we'll see about that.

1 Like