Garuda Maintenance notifications/Snapper rollbacks on Hyprland?

Issues & Assistance Hyprland
1 
> garuda-inxi
System:
  Kernel: 6.12.4-arch1-1 arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: tsc avail: acpi_pm parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux
    root=UUID=0da76497-c423-431f-a389-91bb1acdf968 rw rootflags=subvol=@
    quiet resume=UUID=d0474437-59bc-42b9-a229-f12b8b1ff484 loglevel=3 splash
    ibt=off
  Desktop: Hyprland v: 0.45.2 with: waybar tools: avail: hyprlock vt: 1
    dm: SDDM Distro: Garuda base: Arch Linux
Machine:
  Type: Laptop System: ASUSTeK product: ASUS Vivobook Pro 15 N6506MU_N6506MU
    v: 1.0 serial: <superuser required>
  Mobo: ASUSTeK model: N6506MU v: 1.0 serial: <superuser required>
    uuid: <superuser required> UEFI: American Megatrends LLC. v: N6506MU.308
    date: 08/06/2024
Battery:
  ID-1: BAT0 charge: 73.4 Wh (100.0%) condition: 73.4/75.0 Wh (97.9%)
    volts: 17.4 min: 15.9 model: S560647 type: Unknown serial: <filter>
    status: full cycles: 4
CPU:
  Info: model: Intel Core Ultra 9 185H bits: 64 type: MST AMCP
    arch: Meteor Lake level: v3 note: check built: 2023+ process: Intel 4 (7nm)
    family: 6 model-id: 0xAA (170) stepping: 4 microcode: 0x20
  Topology: cpus: 1x dies: 1 clusters: 9 cores: 16 threads: 22 mt: 6 tpc: 2
    st: 10 smt: enabled cache: 24 MiB note: check
  Speed (MHz): avg: 400 min/max: 400/4800:5100:3800:2500 scaling:
    driver: intel_pstate governor: powersave cores: 1: 400 2: 400 3: 400 4: 400
    5: 400 6: 400 7: 400 8: 400 9: 400 10: 400 11: 400 12: 400 13: 400 14: 400
    15: 400 16: 400 17: 400 18: 400 19: 400 20: 400 21: 400 22: 400
    bogomips: 135212
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities: <filter>
Graphics:
  Device-1: Intel Meteor Lake-P [Intel Arc Graphics] vendor: ASUSTeK
    driver: i915 v: kernel alternate: xe arch: Gen-13 process: Intel 4 (7nm+)
    built: 2023+ ports: active: DP-2,eDP-1 empty: DP-1,DP-3,DP-4
    bus-ID: 0000:00:02.0 chip-ID: 8086:7d55 class-ID: 0300
  Device-2: NVIDIA AD107M [GeForce RTX 4050 Max-Q / Mobile] vendor: ASUSTeK
    driver: nvidia v: 565.77 alternate: nouveau,nvidia_drm non-free: 550.xx+
    status: current (as of 2024-09) arch: Lovelace code: AD1xx
    process: TSMC n4 (5nm) built: 2022+ ports: active: none
    empty: HDMI-A-1,eDP-2 bus-ID: 0000:01:00.0 chip-ID: 10de:28a1
    class-ID: 0300
  Device-3: Shinetech ASUS 5M WebCam driver: hid-sensor-hub,usbhid,uvcvideo
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-9:3
    chip-ID: 3277:0058 class-ID: fe01 serial: <filter>
  Display: wayland server: X.org v: 1.21.1.15 with: Xwayland v: 24.1.4
    compositor: Hyprland v: 0.45.2 driver: X: loaded: modesetting,nvidia
    unloaded: nouveau alternate: fbdev,intel,nv,vesa dri: iris
    gpu: i915,nvidia display-ID: 1
  Monitor-1: DP-2 res: 1920x1080 size: N/A modes: N/A
  Monitor-2: 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: 1 drv: iris gbm: drv: iris surfaceless: drv: nvidia
    wayland: drv: nvidia x11: drv: nvidia
  API: OpenGL v: 4.6.0 compat-v: 4.6 vendor: nvidia mesa v: 565.77
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 4050 Laptop
    GPU/PCIe/SSE2 memory: 5.86 GiB
  API: Vulkan v: 1.4.303 layers: 5 device: 0 type: integrated-gpu name: Intel
    Arc Graphics (MTL) driver: N/A device-ID: 8086:7d55
    surfaces: xcb,xlib,wayland device: 1 type: discrete-gpu name: NVIDIA
    GeForce RTX 4050 Laptop GPU driver: N/A device-ID: 10de:28a1
    surfaces: xcb,xlib,wayland device: 2 type: cpu name: llvmpipe (LLVM
    18.1.8 256 bits) driver: N/A device-ID: 10005:0000
    surfaces: xcb,xlib,wayland
Audio:
  Device-1: Intel Meteor Lake-P HD Audio vendor: ASUSTeK
    driver: sof-audio-pci-intel-mtl
    alternate: snd_hda_intel,snd_sof_pci_intel_mtl bus-ID: 0000:00:1f.3
    chip-ID: 8086:7e28 class-ID: 0401
  API: ALSA v: k6.12.4-arch1-1 status: kernel-api tools: N/A
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: PipeWire v: 1.2.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 Meteor Lake PCH CNVi WiFi driver: iwlwifi v: kernel
    bus-ID: 0000:00:14.3 chip-ID: 8086:7e40 class-ID: 0280
  IF: wlo1 state: up mac: <filter>
  Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK driver: r8169 v: kernel port: 3000 bus-ID: 0000:2d:00.0
    chip-ID: 10ec:8168 class-ID: 0200
  IF: enp45s0 state: down mac: <filter>
  IF-ID-1: virbr0 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: 3-10: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
RAID:
  Hardware-1: Intel Volume Management Device NVMe RAID Controller Intel
    driver: vmd v: 0.6 port: N/A bus-ID: 0000:00:0e.0 chip-ID: 8086:7d0b rev:
    class-ID: 0104
Drives:
  Local Storage: total: 953.87 GiB used: 433.21 GiB (45.4%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital model: WD PC
    SN560 SDDPNQE-1T00-1102 size: 953.87 GiB block-size: physical: 512 B
    logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: 74118000 temp: 56.9 C scheme: GPT
Partition:
  ID-1: / raw-size: 928.44 GiB size: 928.44 GiB (100.00%)
    used: 433.21 GiB (46.7%) 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: 928.44 GiB size: 928.44 GiB (100.00%)
    used: 433.21 GiB (46.7%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-4: /var/log raw-size: 928.44 GiB size: 928.44 GiB (100.00%)
    used: 433.21 GiB (46.7%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-5: /var/tmp raw-size: 928.44 GiB size: 928.44 GiB (100.00%)
    used: 433.21 GiB (46.7%) 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: 22.84 GiB used: 512 KiB (0.0%) priority: 100
    comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 max-streams: 22
    dev: /dev/zram0
  ID-2: swap-2 type: partition size: 25.13 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/nvme0n1p3 maj-min: 259:3
Sensors:
  Src: /sys System Temperatures: cpu: 58.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 24 GiB note: est. available: 22.84 GiB used: 7.53 GiB (33.0%)
  Processes: 476 Power: uptime: 1h 46m states: freeze,mem,disk
    suspend: s2idle avail: deep wakeups: 0 hibernate: platform avail: shutdown,
    reboot, suspend, test_resume image: 9.07 GiB
    services: power-profiles-daemon,upowerd Init: systemd v: 257
    default: graphical tool: systemctl
  Packages: 1883 pm: pacman pkgs: 1872 libs: 483 tools: pacseek,paru
    pm: flatpak pkgs: 11 Compilers: clang: 18.1.8 gcc: 14.2.1 Shell: garuda-inxi
    default: Bash v: 5.2.37 running-in: kitty inxi: 3.3.36
Garuda (2.6.26-1):
  System install date:     2024-11-01
  Last full system update: 2024-12-20
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut nvidia-dkms
  Windows dual boot:       Probably (Run as root to verify)
  Failed units:

Hi,

I have some issues with using Hyprland on my Garuda Linux installation. For context, I have a Garuda Linux Dr460nized installation, on top of which I installed the ML4W dotfiles. So, I have both KDE and Hyprland sessions available on my system.

My issues happen when I log into a Hyprland session. Namely:

  1. the Garuda Maintenance notifications (e.g., about deleting old snapshots) don’t show up in my Waybar’s system tray at all. If I log out and log into a Plasma session, the notifications are there
  2. when I want to restore a Snapper snapshot, I don’t get a dialog window asking whether I want to roll back to that snapshot, after selecting it from the boot menu and logging into Hyprland. I have to log into a Plasma session for the Snapper prompt to appear and to restore the snapshot successfully.

I understand it’s rather unusual to have Hyprland installed alongside KDE. I use Hyprland as my daily driver and KDE as a backup in case something breaks and I can’t access my system anymore. There have been no major issues outside of the 2 I mentioned above.

In case it helps, here’s a screenshot of my Garuda System Maintenance settings:

image
image1411×424 83 KB

Thanks for the help!

2

I think its rather sad you expect the team that maintains Garuda Hyprland to make things work for you when you are using dotfiles not maintained by the garuda team.

So yes, while the notifications can be fixed or are maybe available… they would not work on your system since the dotfiles you are using & the dotfiles garuda maintains are different. This will involve you to manually tweak your ML4W configuration to make them working by observing changes made on garuda dotfiles.

I do think this is a bad idea since it can lead to minor inconviniences like breakage of configurations. Maybe add hyprland to pkgignore, then manually observe changes in updates before updating hyprland if you are paranoid.

3

No need to be so critical. I’m asking for help, not expecting the Garuda team to do anything. If I can get some assistance from here, fine. If not, I’ll just continue searching for solutions.

I’m assuming that getting maintenance notifications running involves maybe executing some app at startup or enabling a service. I just want to see if maybe it’s that simple of a fix, hoping that someone that maintains the Garuda Hyprland spin might know more about this.

And maybe the Snapper prompt at logjn works similarly?

4

The notification daemon is mako, idk maybe adding snapper to exec once on hyprland config. Probably a crontab. Those are options i’d look at., sorry if I seem critical.

5

One tip.
You need to have different user (Accounts) for both. If you use the same account for both configs an such get messed up even if you never touch them.

2 Likes
6

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