Closed pgratz1 closed 1 year ago
I've never had any problems with my K400 Plus. I've run it under most of the recent versions of Solaar and just upgraded Solaar there to version 1.1.8.
In any case Solaar should not have any effect on device input that cannot be controlled using HID++ commands and touchpad movements cannot be controlled using HID++ commands on the K400 Plus. (Some touchpad gestures can be controlled, though.)
You can monitor input from your keyboard at several levels in Linux to investigate what might be going on.
You can see the X events (if you are using X - Wayland may be different) using
xinput test M
To find out which M is for your device look at the output of
xinput
there may be several ids for your device if it produces several kinds of inputs. Pick the one that you are interested in.
If things are working OK then you should see output when you move your finger on the touchpad.
You can see the HID events (which are earlier in input processing) using
sudo evtest /dev/input/eventN
You can just try different N to find out which input is for your keyboard. Look for something like Input device name: "Logitech K400 Plus"
If you see touchpad events here then the keyboard is working fine but something in Linux is messing up. If you don't see touchpad events here then something might be going wrong with your keyboard.
Thanks for the quick reply! See my notes below:
On Wed, Mar 1, 2023 at 10:57 AM Peter F. Patel-Schneider < @.***> wrote:
I've never had any problems with my K400 Plus. I've run it under most of the recent versions of Solaar and just upgraded Solaar there to version 1.1.8.
In any case Solaar should not have any effect on device input that cannot be controlled using HID++ commands and touchpad movements cannot be controlled using HID++ commands on the K400 Plus. (Some touchpad gestures can be controlled, though.)
You can monitor input from your keyboard at several levels in Linux to investigate what might be going on.
You can see the X events (if you are using X - Wayland may be different) using
xinput test M
To find out which M is for your device look at the output of
xinput
there may be several ids for your device if it produces several kinds of inputs. Pick the one that you are interested in.
I found the device number for the keyboard and mouse part of the K400+, the keyboard one works fine with xinput but there are no events for the mouse one.
If things are working OK then you should see output when you move your finger on the touchpad.
You can see the HID events (which are earlier in input processing) using
sudo evtest /dev/input/eventN
You can just try different N to find out which input is for your keyboard. Look for something like Input device name: "Logitech K400 Plus"
I found the one for the K400 Plus but again only keyboard output no mouse output when swiping the touchpad and clicking the buttons.
If you see touchpad events here then the keyboard is working fine but something in Linux is messing up. If you don't see touchpad events here then something might be going wrong with your keyboard.
I'm at a loss because this does seem to work in windows so I don't think its hardware, also it did work in linux a few weeks ago but today when I installed Solaar (to consolodate onto one wireless dongle) it stopped working...
Anything else I can try? Paul
Paul
— Reply to this email directly, view it on GitHub https://github.com/pwr-Solaar/Solaar/issues/2007#issuecomment-1450482887, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADGMOOTXGTR3PBEVCQ7ZDS3WZ55WLANCNFSM6AAAAAAVMHJTE4 . You are receiving this because you authored the thread.Message ID: @.***>
Paul V. Gratz Professor ECE Dept, Texas A&M University Office: 333M WERC Phone: 979-488-4551 http://cesg.tamu.edu/faculty/paul-gratz/
I would try using the keyboard under Windows and then under Linux without Solaar running. If the touchpad works under Windows but not Linux then there probably is something going on with the Linux input driver. If the touchpad works under Linux then try starting Solaar and see if anything changes.
One other thing to check is whether the Unifying receivers are the same. You can see the model of the receivers in the output of lsusb
. The model is the second half of the ID field.
Is there still a problem here?
Sorry for the delay in getting back, I've had a very busy week.
OK so to answer your questions, I had tried it under windows and it works fine there (both keyboard and touch pad). I also tried with two different receivers on linux, no difference.
Now the very strange part, I just turned it on again today and tried it out as I was writing this email and suddenly the touchpad is working fine in linux on the original receiver. I'm at a bit of a loss... My first guess would be flaky hardware but the fact that it worked fine on windows rules that out I think. Not sure if this is worth pursuing further (unless it stops working again). Paul
On Tue, Mar 7, 2023 at 9:20 AM Peter F. Patel-Schneider < @.***> wrote:
Is there still a problem here?
— Reply to this email directly, view it on GitHub https://github.com/pwr-Solaar/Solaar/issues/2007#issuecomment-1458356019, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADGMOOQ3QL2JXR5SVAKH2G3W25G43ANCNFSM6AAAAAAVMHJTE4 . You are receiving this because you authored the thread.Message ID: @.***>
Paul V. Gratz Professor ECE Dept, Texas A&M University Office: 333M WERC Phone: 979-488-4551 http://cesg.tamu.edu/faculty/paul-gratz/
Lots of things have to happen for input devices to work correctly in Linux. Obviously something was going wrong that is now going right. What that is is probably going to remain unknown unless the problem resurfaces.
If the problem does resurface feel free to reopen this issue.
Thanks! Paul
On Wed, Mar 8, 2023 at 11:20 AM Peter F. Patel-Schneider < @.***> wrote:
Closed #2007 https://github.com/pwr-Solaar/Solaar/issues/2007 as completed.
— Reply to this email directly, view it on GitHub https://github.com/pwr-Solaar/Solaar/issues/2007#event-8698724055, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADGMOORT4V6UWUB2K3WUX6LW3C5VJANCNFSM6AAAAAAVMHJTE4 . You are receiving this because you authored the thread.Message ID: @.***>
Paul V. Gratz Professor ECE Dept, Texas A&M University Office: 333M WERC Phone: 979-488-4551 http://cesg.tamu.edu/faculty/paul-gratz/
Sorry for the delay in getting back, I've had a very busy week. OK so to answer your questions, I had tried it under windows and it works fine there (both keyboard and touch pad). I also tried with two different receivers on linux, no difference. Now the very strange part, I just turned it on again today and tried it out as I was writing this email and suddenly the touchpad is working fine in linux on the original receiver. I'm at a bit of a loss... My first guess would be flaky hardware but the fact that it worked fine on windows rules that out I think. Not sure if this is worth pursuing further (unless it stops working again). Paul
Ran into the same issue - taking out the logitech receiver and plugging it in again solved my issue - see also #1510
Basically the title. Solaar does seem to connect to the keyboard just fine, just no response from the touch pad. Interestingly it used to work fine before I installed Solaar (using a different wireless dongle). When I tried to go back to the original dongle with solaar installed it would not connect anymore so I unpaired and repaired on that one and now it has the same behavoir (no touchpad but keyboard works). Tried this on three different Kubuntu machines and both the shipping 1.1.5 and the newer 1.1.8 that I got from Launchpad. No warnings or errors on the console that I launch solaar from.
Here is a screenshot that shows its connected and that it seems to know that there should be a touchpad:
Any help greatly appreciated!
Information
Solaar version (
solaar --version
orgit describe --tags
if cloned from this repository): solaar 1.1.8+dfsg-2Distribution: Kubuntu 22.10
Kernel version (ex.
uname -srmo
): Linux 5.19.0-31-generic x86_64 GNU/LinuxOutput of
solaar show
:~/.config/solaar/config.yaml
(or~/.config/solaar/config.json
if~/.config/solaar/config.yaml
not present):Describe the bug A clear and concise description of what the bug is.
To Reproduce Steps to reproduce the behavior:
Screenshots If applicable, add screenshots to help explain your problem.
Additional context Add any other context about the problem here.