Add/remove software and partition manager do not launch from garuda-welcome

surfr · 30 September 2023 18:46

I just installed the hyprland edition 230929 on an intel laptop. Overall congrats for an awesome install experience and overall functionality!

I noticed that in the garuda-welcome app the following don’t work:

add/remove software causes the welcome to briefly flicker but nothing starts
partition manager causes a prompt for the root password but then garuda-welcome shows up again

garuda-inxi

System:
  Kernel: 6.5.5-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
    clocksource: tsc available: acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=941fde7f-dd53-42fc-87e1-085c47990c6b rw rootflags=subvol=@
    quiet rd.luks.uuid=f4353337-f608-4153-8516-712c2bdd741a
    rd.luks.uuid=bb53fa49-4911-4abe-a164-e31688cc2ebd
    resume=/dev/mapper/luks-bb53fa49-4911-4abe-a164-e31688cc2ebd loglevel=3
    ibt=off
  Desktop: Hyprland info: waybar vt: 1 dm: SDDM Distro: Garuda Linux
    base: Arch Linux
Machine:
  Type: Laptop System: Framework product: Laptop (13th Gen Intel Core) v: A6
    serial: <superuser required>
  Mobo: Framework model: FRANMCCP06 v: A6 serial: <superuser required>
    UEFI: INSYDE v: 03.04 date: 05/24/2023
Battery:
  ID-1: BAT1 charge: 35.9 Wh (58.8%) condition: 61.1/60.7 Wh (100.7%)
    volts: 15.6 min: 15.5 model: NVT FRANGWA type: Li-ion serial: <filter>
    status: discharging cycles: 2
CPU:
  Info: model: 13th Gen Intel Core i7-1360P bits: 64 type: MST AMCP
    arch: Raptor Lake level: v3 note: check built: 2022+ process: Intel 7 (10nm)
    family: 6 model-id: 0xBA (186) stepping: 2 microcode: 0x4119
  Topology: cpus: 1x cores: 12 mt: 4 tpc: 2 st: 8 threads: 16 smt: enabled
    cache: L1: 1.1 MiB desc: d-8x32 KiB, 4x48 KiB; i-4x32 KiB, 8x64 KiB
    L2: 9 MiB desc: 4x1.2 MiB, 2x2 MiB L3: 18 MiB desc: 1x18 MiB
  Speed (MHz): avg: 448 high: 1182 min/max: 400/5000:3700 scaling:
    driver: intel_pstate governor: powersave cores: 1: 400 2: 400 3: 400 4: 1182
    5: 400 6: 400 7: 400 8: 400 9: 400 10: 400 11: 400 12: 400 13: 400 14: 400
    15: 400 16: 400 bogomips: 83558
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities: <filter>
Graphics:
  Device-1: Intel Raptor Lake-P [UHD Graphics] vendor: Framework driver: i915
    v: kernel arch: Gen-13 process: Intel 7 (10nm) built: 2022+ ports:
    active: eDP-1 empty: DP-1, DP-2, DP-3, DP-4 bus-ID: 00:02.0
    chip-ID: 8086:a720 class-ID: 0300
  Device-2: Realtek Laptop Camera driver: uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-7:2 chip-ID: 0bda:5634
    class-ID: 0e02 serial: <filter>
  Display: wayland server: X.org v: 1.21.1.8 with: Xwayland v: 23.2.1
    compositor: Hyprland driver: X: loaded: modesetting
    alternate: fbdev,intel,vesa dri: iris gpu: i915 display-ID: 1
  Monitor-1: eDP-1 model: BOE Display 0x0bca built: 2022 res: 2256x1504
    hz: 60 dpi: 201 gamma: 1.2 scale: 1 size: 285x190mm (11.22x7.48")
    diag: 343mm (13.5") ratio: 3:2 modes: 2256x1504
  API: Vulkan v: 1.3.264 layers: 4 device: 0 type: integrated-gpu
    name: Intel Graphics (RPL-P) driver: mesa intel v: 23.1.8-arch1.1
    device-ID: 8086:a720 surfaces: xcb,xlib,wayland device: 1 type: cpu
    name: llvmpipe (LLVM 16.0.6 256 bits) driver: mesa llvmpipe
    v: 23.1.8-arch1.1 (LLVM 16.0.6) device-ID: 10005:0000
    surfaces: xcb,xlib,wayland
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
Audio:
  Device-1: Intel Raptor Lake-P/U/H cAVS vendor: Framework
    driver: snd_hda_intel v: kernel alternate: snd_sof_pci_intel_tgl
    bus-ID: 00:1f.3 chip-ID: 8086:51ca class-ID: 0403
  API: ALSA v: k6.5.5-zen1-1-zen status: kernel-api tools: N/A
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: PipeWire v: 0.3.80 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Wi-Fi 6 AX210/AX211/AX411 160MHz driver: iwlwifi v: kernel
    pcie: gen: 2 speed: 5 GT/s lanes: 1 bus-ID: aa:00.0 chip-ID: 8086:2725
    class-ID: 0280
  IF: wlp170s0 state: up mac: <filter>
Bluetooth:
  Device-1: Intel AX210 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-10:4 chip-ID: 8087:0032
    class-ID: e001
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.3
    lmp-v: 12 status: discoverable: no pairing: no class-ID: 6c010c
Drives:
  Local Storage: total: 991.14 GiB used: 16.64 GiB (1.7%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital
    model: WD BLACK SN850X 1000GB size: 931.51 GiB block-size: physical: 512 B
    logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: 620311WD temp: 30.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: SMI (STMicroelectronics)
    model: USB DISK size: 59.62 GiB block-size: physical: 512 B logical: 512 B
    type: USB rev: 3.0 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: N/A
    serial: <filter> fw-rev: 1100 scheme: MBR
Partition:
  ID-1: / raw-size: 897.05 GiB size: 897.05 GiB (100.00%)
    used: 12.39 GiB (1.4%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
    mapped: luks-f4353337-f608-4153-8516-712c2bdd741a
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 720 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-3: /home raw-size: 897.05 GiB size: 897.05 GiB (100.00%)
    used: 12.39 GiB (1.4%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
    mapped: luks-f4353337-f608-4153-8516-712c2bdd741a
  ID-4: /var/log raw-size: 897.05 GiB size: 897.05 GiB (100.00%)
    used: 12.39 GiB (1.4%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
    mapped: luks-f4353337-f608-4153-8516-712c2bdd741a
  ID-5: /var/tmp raw-size: 897.05 GiB size: 897.05 GiB (100.00%)
    used: 12.39 GiB (1.4%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
    mapped: luks-f4353337-f608-4153-8516-712c2bdd741a
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: partition size: 34.17 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/dm-1 maj-min: 254:1
    mapped: luks-bb53fa49-4911-4abe-a164-e31688cc2ebd
  ID-2: swap-2 type: zram size: 31.06 GiB used: 0 KiB (0.0%) priority: 100
    comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 16 dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 38.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Processes: 370 Uptime: 1h 34m wakeups: 60388 Memory: total: 32 GiB
  note: est. available: 31.06 GiB used: 3.23 GiB (10.4%) Init: systemd v: 254
  default: graphical tool: systemctl Compilers: gcc: 13.2.1 Packages:
  pm: pacman pkgs: 1319 libs: 395 tools: paru Shell: fish v: 3.6.1
  running-in: foot inxi: 3.3.30
Garuda (2.6.16-1):
  System install date:     2023-09-30
  Last full system update: 2023-09-30 ↻
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut
  Windows dual boot:       Probably (Run as root to verify)
  Failed units:

SGS · 30 September 2023 19:39

Thanks for the note, since we no longer ship pamac with the DE’s we have yet to remove it from garuda-welcome.

There are problems with Wayland, if I’m not mistaken.

Just start it in the terminal

sudo -E gparted

We recommend Hyprland only for experienced users, it may break down more often.

surfr · 30 September 2023 19:51

Breakage is OK, I’m just flagging it…

BluishHumility · 1 October 2023 16:10

Fixed in this MR:

I was going to take a look at this too, but it appears someone already beat me to it.

ThorpeJosh · 17 October 2023 03:16

I’m facing the same issue with Gardua Boot Options. Only way I can get it to launch is running sudo -E garuda-boot-options.

I couldn’t see a patch for this in the MR above. You guys having issues with boot options?

BluishHumility · 17 October 2023 03:30

When I tested, launching Garuda Boot Options with /usr/lib/garuda/pkexec-gui garuda-boot-options was working (this is the command Garuda Welcome uses). If that isn’t working, perhaps something is not right in your environment.

Are you logging in with the “Garuda Hyprland” profile on SDDM?

ThorpeJosh · 17 October 2023 05:40

Yeah confirmed I am logged into Garuda Hyprland.

$ /usr/lib/garuda/pkexec-gui garuda-boot-options
Failed to create wl_display (Not a directory)
qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found.
Authorization required, but no authorization protocol specified

qt.qpa.xcb: could not connect to display :1
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, '/usr/lib/garuda/pkexec-gui garu…' terminated by signal SIGABRT (Abort)

BluishHumility · 17 October 2023 10:36

Edit:

I figured out why it wasn’t working. I made a mistake when I changed /usr/lib/garuda/pkexec-gui and added QT_STYLE_OVERRIDE to the export WAYLAND_DISPLAY= line when it should have only been added to the while IFS= line.

I fixed my mistake here:

Next time you update garuda-libs (to 1.4.4) it should be working again. If you can take a look and confirm when you have a chance I would appreciate it.

I also added QT_QPA_PLATFORMTHEME to the environment variables that get preserved in case someone is not using QT_STYLE_OVERRIDE, so it was good to take another look anyway.

system · 19 October 2023 10:37

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.