Open mikkurogue opened 1 month ago
Please post the output of solaar -ddd
from startup through an idle cycle (after killing any running Solaar).
output solaar -ddd
was idle before this for about an hour - when dpi was set to 600
This is an interaction between the DPI and device profiles. Device profiles sets the DPI, which now silently overrides the DPI setting. This is a feature, but something should be done to either change or better explain the behaviour.
What i dont understand is that when I used Garuda and hyprland, the setting dpi wasn't overwritten by the on-board profile, as long as Solaar was active it would keep the dpi at the setting I set it to. Even after idling or rebooting. All I had to do was make sure that my hyprland.conf
had the exec-once = solaar
enabled so it would run and set the config.
I'm sure I'm missing something in terms of utility or a lib in Arch but I wouldnt know what yet
I think this was a somewhat inadvertent effect of adding more support for onboard profiles in Solaar.
I am facing the same issue. Any way to fix this ?
Not necessarily, i basically just booted into windows and removed all onboard profiles and changed them to have 1 dpi so it never changes.
Not a great solution but it works for now until we get a solaar update i guess
You can use Solaar to update onboard profiles, but you have to dump, edit, and reload the profile. You can use onboard profiles to do some useful things.
The question is what the behaviour should be with respect to onboard profiles and the settings that they impact. How does Logitech software work? Is that a good way to handle things in Solaar?
The way G Hub works on Windows is that you can toggle between the onboard profiles and the G Hub profiles. By default onboard profiles (at least for the G502 X LS) are unused unless selected, otherwise it has a few programatic profiles (like the solaar config, but presistent in G Hub).
I'm not sure how this works for other devices, I have a Logitech MX Master 2S I could try later on.
I wouldn't really know if Solaar has the capability to allow users to disable the usage of the onboard profiles in favour of persistent software created profiles (like the config.yaml file)
If you set Onboard Profiles to Disabled the value for the Sensitivity (DPI) setting will be used instead of the DPI from the profile. You do lose whatever abilities Onboard Profiles gives you (such as buttons that can cycle through different DPIs).
You can think of Onboard Profiles Disabled as a (single) G Hub profile defined by the Solaar settings, although it may not have all the features of a G Hub profile.
There should be better documentation of this interaction.
You do lose whatever abilities Onboard Profiles gives you (such as buttons that can cycle through different DPIs).
Does this also work like this in GHub with the onboard profiles disabled? As far as I know the G Hub profiles also allow you to store DPI steps to keep the button functionality (Not like I use this, I stick my good ol' faithful 600 DPI at all times). More so for those who do value DPI toggling.
@pfps
You can use Solaar to update onboard profiles, but you have to dump, edit, and reload the profile. You can use onboard profiles to do some useful things.
How would i do that? I dont see anything related to profile in solaar
Solaar has a command-line interface. solaar --help
describes the actions. solaar profiles <device> [<profiles>]
dumps or loads the profiles.
Also having this issue, settings keep resetting. This is the only program I've found that works with the G502 X LS, can Solaar handle the extra G buttons? Or does anyone know software that can? Piper is abandoned at this point.
Solaar has a command-line interface.
solaar --help
describes the actions.solaar profiles <device> [<profiles>]
dumps or loads the profiles.
Thanks i ll look at it. Still feels like Solaar should be handling that:
I dont know if it is related but i have another issue with the middle button not working (closing tabs...) if solaar is started after the mouse is connected. it happens on boot on resume. I keep on having to restart my mouse
When there are two ways to set a feature (DPI) a system has to make a choice. Solaar has made the choice that if Onboard Profiles are enabled then that overrides other ways of setting features that the profiles control.
If you have having different problems you should open an issue about them.
When there are two ways to set a feature (DPI) a system has to make a choice. Solaar has made the choice that if Onboard Profiles are enabled then that overrides other ways of setting features that the profiles control.
I dont think it is a question of having 2 ways of setting a feature. But more about which one have to be seen as the default / primary one. It is exactly the same as when you talk about app dark mode. The system provides a default but if the settings in the app overrides it then you use the setting of the app. As an app dev this is how i would do it and i think it is the way most user would understand it.
If you have having different problems you should open an issue about them.
Indeed will do thanks
Well, yes, it is precisely about which method is primary. Solaar takes the view that profiles is primary. As far as I can tell, this method is the only possible one for Solaar because for some settings enabling onboard profiles means that the setting cannot be changed except using profiles.
Well, yes, it is precisely about which method is primary. Solaar takes the view that profiles is primary. As far as I can tell, this method is the only possible one for Solaar because for some settings enabling onboard profiles means that the setting cannot be changed except using profiles.
You mean you cant change on setting without changing the whole profile? I dont want to try to say you are wrong or anything. You are the dev you know best how it works. What bothers me is that even if it is a question of the way profiles works it really simply feels like a bug in the sense that it works when you trigger the dpi toggle off and on again. If it works in this case it should work all the time (app boot, mouse restart...). And to me the behavior i get when i trigger the toggle to on is app setting overriding profile setting (if i understand it correctly).
DPI is a setting that for some devices can be changed when profiles are active. But Solaar can't know whether this is true for all devices.
Information
uname -srmo
):Linux 6.9.10-arch1-1
solaar show
:~/.config/solaar/config.yaml
(or~/.config/solaar/config.json
if~/.config/solaar/config.yaml
not present):Describe the bug I recently swapped my distro from Garuda Linux to just Arch Linux, and in Garuda it was working fine.
Now however, I have to manually reset the DPI after each idle or reboot. The config.yaml is written when I save but then it resets/is removed after a reboot. Funnily enough, the profiles and report rate setting is kept just fine.
To Reproduce Steps to reproduce the behavior:
yay -S solaar-git
Screenshots If applicable, add screenshots to help explain your problem.
Additional context I did go through arch docs to also add solaar to the
plugdev
user group, but this still didn't do much. Here the output ofgroups <username>
:I did also find similar issues but none of the solutions worked there for me, so I probably think I'm missing a lib or some other setting that Garuda Linux did have and I don't on a fresh Arch installation. On both distros I did run wayland with hyprland, the functionality is all the same except that the settings arent saved on the fresh Arch install