Failed to start garuda-fish-completions-update.service

Issues & Assistance
1

Hey, so I'm not sure what happened here exactly, but I updated my system and got the following error.

Failed to start garuda-fish-completions-update.service: Transport endpoint is not connected
See user logs and 'systemctl --user status garuda-fish-completions-update.service' for details.

Here is the output of what it suggested.

garuda-fish-completions-update.service - Updates fish completions
     Loaded: loaded (/usr/lib/systemd/user/garuda-fish-completions-update.service; static)
     Active: inactive (dead)

And finally, my garuda-inxi. Thanks for any help.

System:
  Kernel: 5.19.0-1-bore arch: x86_64 bits: 64 compiler: gcc v: 12.1.0
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-bore
    root=UUID=95b636ca-42a5-47b4-9b7a-038581af6cdf rw rootflags=subvol=@
    mitigations=off quiet splash rd.udev.log_priority=3
    vt.global_cursor_default=0
    resume=UUID=41193397-191d-45b5-8c2b-405cf71e73b2 loglevel=3
  Desktop: KDE Plasma v: 5.25.4 tk: Qt v: 5.15.5 info: latte-dock
    wm: kwin_wayland vt: 2 dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
  Type: Laptop System: ASUSTeK product: X510UA v: 1.0
    serial: <superuser required>
  Mobo: ASUSTeK model: X510UA v: 1.0 serial: <superuser required>
    UEFI: American Megatrends v: X510UA.312 date: 04/29/2020
Battery:
  ID-1: BAT0 charge: 5.5 Wh (20.4%) condition: 26.9/42.1 Wh (63.9%)
    volts: 11.5 min: 11.5 model: ASUSTeK ASUS Battery type: Li-ion serial: N/A
    status: discharging cycles: 495
CPU:
  Info: model: Intel Core i7-7500U bits: 64 type: MT MCP
    arch: Amber/Kaby Lake note: check gen: core 7 built: 2017
    process: Intel 14nm family: 6 model-id: 0x8E (142) stepping: 9
    microcode: 0xF0
  Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache:
    L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB
    L3: 4 MiB desc: 1x4 MiB
  Speed (MHz): avg: 496 high: 500 min/max: 400/3500 scaling:
    driver: intel_pstate governor: powersave cores: 1: 500 2: 500 3: 489 4: 497
    bogomips: 23220
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: vulnerable
  Type: mds status: Vulnerable; SMT vulnerable
  Type: meltdown status: Vulnerable
  Type: mmio_stale_data status: Vulnerable
  Type: retbleed status: Vulnerable
  Type: spec_store_bypass status: Vulnerable
  Type: spectre_v1 status: Vulnerable: __user pointer sanitization and
    usercopy barriers only; no swapgs barriers
  Type: spectre_v2 status: Vulnerable, IBPB: disabled, STIBP: disabled
  Type: srbds status: Vulnerable
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel HD Graphics 620 vendor: ASUSTeK driver: i915 v: kernel
    arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports: active: eDP-1
    empty: HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:5916 class-ID: 0300
  Device-2: IMC Networks VGA UVC WebCam type: USB driver: uvcvideo
    bus-ID: 1-6:2 chip-ID: 13d3:5a07 class-ID: 0e02 serial: <filter>
  Display: wayland server: X.org v: 1.21.1.4 with: Xwayland v: 22.1.3
    compositor: kwin_wayland driver: X: loaded: modesetting
    alternate: fbdev,intel,vesa gpu: i915 display-ID: 0
  Monitor-1: eDP-1 res: 1920x1080 size: N/A modes: N/A
  OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 22.1.4
    direct render: Yes
Audio:
  Device-1: Intel Sunrise Point-LP HD Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel alternate: snd_soc_skl,snd_soc_avs
    bus-ID: 00:1f.3 chip-ID: 8086:9d71 class-ID: 0403
  Sound Server-1: ALSA v: k5.19.0-1-bore running: yes
  Sound Server-2: PulseAudio v: 16.1 running: no
  Sound Server-3: PipeWire v: 0.3.56 running: yes
Network:
  Device-1: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 bus-ID: 02:00.0 chip-ID: 8086:24fd class-ID: 0280
  IF: wlp2s0 state: up mac: <filter>
  IF-ID-1: virbr0 state: down mac: <filter>
Bluetooth:
  Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8
    bus-ID: 1-8:3 chip-ID: 8087:0a2b class-ID: e001
  Report: bt-adapter ID: hci0 rfk-id: 0 state: down
    bt-service: enabled,running rfk-block: hardware: no software: yes
    address: <filter>
Drives:
  Local Storage: total: 931.52 GiB used: 265.14 GiB (28.5%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 870 EVO 500GB
    size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    type: SSD serial: <filter> rev: 1B6Q scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 860 EVO M.2 500GB
    size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    type: SSD serial: <filter> rev: 1B6Q scheme: GPT
Partition:
  ID-1: / raw-size: 448.4 GiB size: 448.4 GiB (100.00%) used: 119.83 GiB
    (26.7%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%) used: 32.1 MiB
    (10.7%) fs: vfat dev: /dev/sda1 maj-min: 8:1
  ID-3: /home raw-size: 448.4 GiB size: 448.4 GiB (100.00%) used: 119.83
    GiB (26.7%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
  ID-4: /var/log raw-size: 448.4 GiB size: 448.4 GiB (100.00%) used: 119.83
    GiB (26.7%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
  ID-5: /var/tmp raw-size: 448.4 GiB size: 448.4 GiB (100.00%) used: 119.83
    GiB (26.7%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: zram size: 15.52 GiB used: 2.2 MiB (0.0%)
    priority: 100 dev: /dev/zram0
  ID-2: swap-2 type: partition size: 17.06 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/sda3 maj-min: 8:3
Sensors:
  System Temperatures: cpu: 53.0 C pch: 42.5 C mobo: N/A
  Fan Speeds (RPM): cpu: 2900
Info:
  Processes: 267 Uptime: 11m wakeups: 1 Memory: 15.52 GiB used: 4.19 GiB
  (27.0%) Init: systemd v: 251 default: graphical tool: systemctl
  Compilers: gcc: 12.1.1 clang: 14.0.6 Packages: pacman: 1580 lib: 375
  Shell: fish v: 3.5.1 running-in: yakuake inxi: 3.3.20
Garuda (2.6.5-1):
  System install date:     2022-05-27
  Last full system update: 2022-08-03
  Is partially upgraded:   No
  Relevant software:       NetworkManager
  Windows dual boot:       Probably (Run as root to verify)
  Snapshots:               Snapper
  Failed units:            mnt-backups.mount systemd-sysctl.service
2

Looks like you are not the only one:
https://forum.garudalinux.org/t/sudo-garuda-update-failed/21186/2

1 Like
3

Yeah I noticed after posting he'd posted a minute earlier while I was making my post lol. He didn't include anything useful other than the error though. Maybe this is a widespread problem if we both got it similar time though? Maybe some mirror or configuration somewhere? No clue so I'll wait for someone who knows hopefully

4

Here's my journal output btw in case it helps.

https://bin.garudalinux.org/?08a2309bcce412c7=#FemyNwT3mxHagDdQpQHGTFD9aKXVuDNVnwT1yEgwzX7m

5

I got following

systemctl --user status garuda-fish-completions-update.service
○ garuda-fish-completions-update.service - Updates fish completions
     Loaded: loaded (/usr/lib/systemd/user/garuda-fish-completions-update.service; static)
     Active: inactive (dead)

Aug 03 10:51:35 i3 systemd[10534]: Starting Updates fish completions...
Aug 03 10:51:35 i3 fish[33079]: Parsing man pages and writing completions to /home/sgs/.local/share/fish/gener>
Aug 03 10:51:38 i3 fish[33079]: [48.0K blob data]
Aug 03 10:51:39 i3 fish[33079]: [47.9K blob data]
Aug 03 10:51:41 i3 fish[33079]: [48.0K blob data]
Aug 03 10:51:41 i3 fish[33079]: [24.8K blob data]
Aug 03 10:51:41 i3 systemd[10534]: Finished Updates fish completions.
Aug 03 10:51:41 i3 systemd[10534]: garuda-fish-completions-update.service: Consumed 6.144s CPU time.

So, try

systemctl --user start --now garuda-fish-completions-update.service

or

systemctl --user enable --now garuda-fish-completions-update.service
6

Hey, so starting this service worked so thanks for that. I’m still concerned how it became inactive though as that’s worried me incase it happens elsewhere too. I did try enabling the service once I confirmed starting it worked but got the following message.

The unit files have no installation config (WantedBy=, RequiredBy=, Also=,
Alias= settings in the [Install] section, and DefaultInstance= for template
units). This means they are not meant to be enabled using systemctl.
 
Possible reasons for having this kind of units are:
• A unit may be statically enabled by being symlinked from another unit's
  .wants/ or .requires/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
  a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
  D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
  instance name specified.
7

It now looks like this under systemctl status but I would like to have this work at bootup like before.

○ garuda-fish-completions-update.service - Updates fish completions
     Loaded: loaded (/usr/lib/systemd/user/garuda-fish-completions-update.service; static)
     Active: inactive (dead)

Aug 03 17:02:58 adam-x510ua fish[3313]: [43.9K blob data]
Aug 03 17:02:58 adam-x510ua systemd[1223]: Finished Updates fish completions.
Aug 03 17:02:58 adam-x510ua systemd[1223]: garuda-fish-completions-update.service: Consumed 10.159s CPU time.
Aug 03 17:03:19 adam-x510ua systemd[1223]: Starting Updates fish completions...
Aug 03 17:03:19 adam-x510ua fish[3581]: Parsing man pages and writing completions to /home/adamj/.local/share/fish/generated_completions/
Aug 03 17:03:24 adam-x510ua fish[3581]: [48.0K blob data]
Aug 03 17:03:27 adam-x510ua fish[3581]: [48.0K blob data]
Aug 03 17:03:29 adam-x510ua fish[3581]: [43.9K blob data]
Aug 03 17:03:29 adam-x510ua systemd[1223]: Finished Updates fish completions.
Aug 03 17:03:29 adam-x510ua systemd[1223]: garuda-fish-completions-update.service: Consumed 10.088s CPU time.
8
4 Likes
9

Perfect. Thanks for letting me know

1 Like
10

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