You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I have installed EndeavourOS and Hyprland onto a Surface Pro 4 as I am attempting to create a customized tablet configuration. I have successfully installed hyprgrass and it is enabled. I have restarted the device several times. Normal touch inputs are being detected by hyprland and I can interact with waybar, firefox, and alacritty by touching the screen.
Custom gestures, or really hyprgrass as a whole, doesn't appear to be working. I attempted to create some gestures for testing that would send notifications, but nothing happens. I have also tested having some gestures that open applications, and those do not work either.
Log
I enabled logging as described in other recent issues, but nothing related to hyprgrass is being logged. I can provide them if necessary, but they just show libinput detecting a gesture, or tap, but none of the logs I have seen present in other issues appear in the logs for me, ie: hypgrass never appears in the log, nor any attempt to match the gesture to a binding.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
OS: EndeavourOS
output of hyprctl version or Hyprland -v:
Hyprland 0.47.2 built from branch at commit 882f7ad7d2bbfc7440d0ccaef93b1cdd78e8e3ff (version: bump to 0.47.2).
Date: Sun Feb 2 00:47:17 2025
Tag: v0.47.2, commits: 5767
built against:
aquamarine 0.7.2
hyprlang 0.6.0
hyprutils 0.5.0
hyprcursor 0.1.11
hyprgraphics 0.1.1
no flags were set
output of hyprctl plugin list:
no plugins loaded
Additional context
hyprpm list shows hyprgrass installed and enabled, I am not sure why hypctl plugin list is different, but I now suspect that might be the culprit. I am submitting this now despite this and will continue to try to get it working.
The text was updated successfully, but these errors were encountered:
I was unable to find any indication of a crash, hyprgrass, or error of any kind in the logs, though I was just looking for keywords since I am still new to hyprland.
hmm looks like hyprpm isn't doing its job. Did you do this:
You can add exec-once = hyprpm reload -n to your hyprland config to have plugins loaded at startup. -n will make hyprpm send a notification if anything goes wrong (e.g. update needed)
also check the wiki about hyprpm, I don't use hyprpm myself so I'm not really sure what's going on
You can also try installing another plugin, if that works correctly, the problem might not be hyprpm
Describe the bug
I have installed EndeavourOS and Hyprland onto a Surface Pro 4 as I am attempting to create a customized tablet configuration. I have successfully installed hyprgrass and it is enabled. I have restarted the device several times. Normal touch inputs are being detected by hyprland and I can interact with waybar, firefox, and alacritty by touching the screen.
Custom gestures, or really hyprgrass as a whole, doesn't appear to be working. I attempted to create some gestures for testing that would send notifications, but nothing happens. I have also tested having some gestures that open applications, and those do not work either.
Log
I enabled logging as described in other recent issues, but nothing related to hyprgrass is being logged. I can provide them if necessary, but they just show libinput detecting a gesture, or tap, but none of the logs I have seen present in other issues appear in the logs for me, ie: hypgrass never appears in the log, nor any attempt to match the gesture to a binding.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
hyprctl version
orHyprland -v
:hyprctl plugin list
:Additional context
hyprpm list shows hyprgrass installed and enabled, I am not sure why hypctl plugin list is different, but I now suspect that might be the culprit. I am submitting this now despite this and will continue to try to get it working.
The text was updated successfully, but these errors were encountered: