Bauh Package Manager Does Not Show Snaps (even installed)

Hi Folks

For some reason bauh package manager is not showing snaps. I have 2 installed and it should show them installed even if the server is down. It was working fine up to a couple days ago.

Has anyone heard of anything?

garuda-inxi
System:
Kernel: 6.9.3-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.1.1
clocksource: tsc avail: acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=2cf2998d-8548-4a0c-ad3c-2aac11f9ec10 rw rootflags=subvol=@
quiet loglevel=3 nvidia_drm.modeset=1 ibt=off
Desktop: KDE Plasma v: 6.0.5 tk: Qt v: N/A info: frameworks v: 6.2.0
wm: kwin_wayland with: krunner vt: 1 dm: SDDM Distro: Garuda
base: Arch Linux
Machine:
Type: Laptop System: System76 product: Adder WS v: addw3
serial: <superuser required> Chassis: type: 9 serial: <superuser required>
Mobo: System76 model: Adder WS v: addw3 serial: <superuser required>
UEFI: coreboot v: 2023-09-19_16ef69c date: 09/15/2023
Battery:
ID-1: BAT0 charge: 63.4 Wh (89.9%) condition: 70.5/70.8 Wh (99.6%)
volts: 17.0 min: 15.4 model: Notebook BAT type: Li-ion serial: <filter>
status: not charging cycles: 1
Device-1: hidpp_battery_0 model: Logitech Wireless Mouse serial: <filter>
charge: 55% (should be ignored) rechargeable: yes status: discharging
CPU:
Info: model: 13th Gen Intel Core i9-13900HX bits: 64 type: MST AMCP
arch: Raptor Lake gen: core 13 level: v3 note: check built: 2022+
process: Intel 7 (10nm) family: 6 model-id: 0xB7 (183) stepping: 1
microcode: 0x123
Topology: cpus: 1x cores: 24 mt: 8 tpc: 2 st: 16 threads: 32 smt: enabled
cache: L1: 2.1 MiB desc: d-16x32 KiB, 8x48 KiB; i-8x32 KiB, 16x64 KiB
L2: 32 MiB desc: 8x2 MiB, 4x4 MiB L3: 36 MiB desc: 1x36 MiB
Speed (MHz): avg: 835 high: 1264 min/max: 800/5200:5400:3900 scaling:
driver: intel_pstate governor: powersave cores: 1: 800 2: 800 3: 800 4: 800
5: 800 6: 800 7: 800 8: 800 9: 985 10: 800 11: 925 12: 808 13: 800 14: 800
15: 800 16: 800 17: 1264 18: 1145 19: 800 20: 800 21: 800 22: 800 23: 800
24: 800 25: 800 26: 800 27: 800 28: 800 29: 800 30: 800 31: 800 32: 800
bogomips: 154828
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel Raptor Lake-S UHD Graphics vendor: CLEVO/KAPOK driver: i915
v: kernel alternate: xe arch: Gen-13 process: Intel 7 (10nm) built: 2022+
ports: active: eDP-1 empty: DP-1, DP-2, DP-3, HDMI-A-1, HDMI-A-2, HDMI-A-3
bus-ID: 00:02.0 chip-ID: 8086:a788 class-ID: 0300
Device-2: NVIDIA AD107M [GeForce RTX 4060 Max-Q / Mobile]
vendor: CLEVO/KAPOK driver: nvidia v: 550.78 alternate: nouveau,nvidia_drm
non-free: 550.xx+ status: current (as of 2024-04) arch: Lovelace
code: AD1xx process: TSMC n4 (5nm) built: 2022+ pcie: gen: 4
speed: 16 GT/s lanes: 8 ports: active: none empty: DP-4,HDMI-A-4,eDP-2
bus-ID: 01:00.0 chip-ID: 10de:28a0 class-ID: 0300
Device-3: Bison BisonCam NB Pro driver: uvcvideo type: USB rev: 2.0
speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-11:3 chip-ID: 5986:9102
class-ID: 0e02
Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 24.1.0
compositor: kwin_wayland driver: X: loaded: modesetting,nvidia dri: iris
gpu: i915,nvidia display-ID: 0
Monitor-1: eDP-1 res: 1920x1080 size: N/A modes: N/A
API: EGL v: 1.5 hw: drv: intel iris drv: nvidia platforms: device: 0
drv: nvidia device: 2 drv: iris device: 3 drv: swrast gbm: drv: nvidia
surfaceless: drv: nvidia wayland: drv: iris x11: drv: iris
inactive: device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: intel mesa v: 24.1.1-arch1.1
glx-v: 1.4 direct-render: yes renderer: Mesa Intel Graphics (RPL-S)
device-ID: 8086:a788 memory: 15.23 GiB unified: yes display-ID: :1.0
API: Vulkan v: 1.3.279 layers: 4 device: 0 type: integrated-gpu
name: Intel Graphics (RPL-S) driver: mesa intel v: 24.1.1-arch1.1
device-ID: 8086:a788 surfaces: xcb,xlib,wayland device: 1
type: discrete-gpu name: NVIDIA GeForce RTX 4060 Laptop GPU driver: nvidia
v: 550.78 device-ID: 10de:28a0 surfaces: xcb,xlib,wayland device: 2
type: cpu name: llvmpipe (LLVM 17.0.6 256 bits) driver: mesa llvmpipe
v: 24.1.1-arch1.1 (LLVM 17.0.6) device-ID: 10005:0000
surfaces: xcb,xlib,wayland
Audio:
Device-1: Intel Raptor Lake High Definition Audio vendor: CLEVO/KAPOK
driver: snd_hda_intel v: kernel alternate: snd_soc_avs,snd_sof_pci_intel_tgl
bus-ID: 00:1f.3 chip-ID: 8086:7a50 class-ID: 0403
Device-2: NVIDIA driver: snd_hda_intel v: kernel pcie: gen: 4
speed: 16 GT/s lanes: 8 bus-ID: 01:00.1 chip-ID: 10de:22be class-ID: 0403
API: ALSA v: k6.9.3-zen1-1-zen status: kernel-api tools: N/A
Server-1: PipeWire v: 1.0.7 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 Raptor Lake-S PCH CNVi WiFi driver: iwlwifi v: kernel
bus-ID: 00:14.3 chip-ID: 8086:7a70 class-ID: 0280
IF: wlp0s20f3 state: up mac: <filter>
Device-2: Intel vendor: CLEVO/KAPOK driver: e1000e v: kernel port: N/A
bus-ID: 00:1f.6 chip-ID: 8086:0dc8 class-ID: 0200
IF: eno0 state: down mac: <filter>
Info: services: NetworkManager, smbd, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: Intel AX211 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-14:4 chip-ID: 8087:0033
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: 931.51 GiB used: 11.36 GiB (1.2%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 980 PRO 1TB
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: 5B2QGXA7 temp: 45.9 C
scheme: GPT
Partition:
ID-1: / raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 11.36 GiB (1.2%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 584 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 11.36 GiB (1.2%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-4: /var/log raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 11.36 GiB (1.2%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-5: /var/tmp raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 11.36 GiB (1.2%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 31.19 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 32 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 61.0 C mobo: N/A
Fan Speeds (rpm): cpu: 1727
Info:
Memory: total: 32 GiB note: est. available: 31.19 GiB used: 3.29 GiB (10.6%)
Processes: 497 Power: uptime: 32m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 12.43 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 255 default: graphical
tool: systemctl
Packages: 1472 pm: pacman pkgs: 1464 libs: 418 tools: pamac,paru
pm: flatpak pkgs: 0 pm: snap pkgs: 8 Compilers: gcc: 14.1.1
Shell: garuda-inxi default: fish v: 3.7.1 running-in: konsole inxi: 3.3.34
Garuda (2.6.26-1):
System install date:     2024-06-08
Last full system update: 2024-06-08
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut nvidia-dkms
Windows dual boot:       No/Undetected
Failed units:

That you need to take up witrh the maintainer of Bauh.

2 Likes

Thanks for the quick response.

Would you happen to know where the ‘.conf’ file would be located for bauh?

I don’t know if this is what you need, but a good reading in general could help anyway:

3 Likes

Thanks

No I do not know where it is cause I’ve never had reason to have to edit it. As for Snaps only install as a last resort. Repos first, AUR if necessary, Flatpaks and or App Images.

Hi there

I just use Snaps for some games Flatpak doesn’t have yet. As for Bauh, the Appimage works just fine. This is what the developer recommends. That’s the solution for now. Some how, the latest compilation in the chaotic-aur seems to have affected the package in some way.

Thanks all

1 Like

Yea I always use bauh-staging cause it work time and time again where the so called stable version isn’t always so stable.

Bauh to list updates, upd to for system updates and those from the main repos, topgrade to update everuthing else.