Comments (59)
ldrahnik
commented on August 15, 2024
2
@irvng-wav The problem with setting up the last brightness should be fixed by the latest commit.
from asus-numberpad-driver.
ldrahnik
commented on August 15, 2024
1
It doesn't look like yours.
Because I have had already added a lot of shorcuts for achieving multiple goals and than I have installed this driver which adds only one shortcut for toggling calculator - that Is why.
from asus-numberpad-driver.
ldrahnik
commented on August 15, 2024
1
I installed the master branch fixed to the commit 66649a9 but then the problematic behavior that I described in the first post returned: numpad didn't work and cpu usage became high.
Thank you, that was my mistake pointing you to that commit.
from asus-numberpad-driver.
irvng-wav
commented on August 15, 2024
1
@irvng-wav May I close this issue as completed? or any problem persists?
Will test in the morning and report back to you. It's sleep time on this side of the world. 😜
from asus-numberpad-driver.
irvng-wav
commented on August 15, 2024
1
Cleared the log, changed the activation values to 0.3 seconds for on/off and 0.4 seconds for changing brightness, rebooted, and everything is also working perfectly right after boot! I'm not having any issues. Brightness state is saved and recalled correctly, even on reboot. Calculator toggle is also working perfectly!
I think you might have done it, man! Here's the continuation of error.log
error.log
Will keep testing for a day or two and report back if I find something.
Thank you man!
from asus-numberpad-driver.
irvng-wav
commented on August 15, 2024
1
Hey @ldrahnik! The only thing I found is that sometimes the brightness level resets to the maximum. This happened like two times when I left the computer turned off for maybe a day. Also recently I've been using mostly Windows in this laptop due to my job, so sometimes when it's been a while (a day or more) since I used Linux and I log back in to it, the numpad brightness is reset. I don't know if that's normal.
Other than that it's been a stable experience. If you want you can go ahead and close this issue and I can open a new issue for that small thing if that's something you feel it's worth looking at.
Thank you!
from asus-numberpad-driver.
ldrahnik
commented on August 15, 2024
@irvng-wav Thank you for reporting. Until will be fixed please use the master branch fixed to the commit 2aae615 (recommended) or previous release tag v5.1.1.
from asus-numberpad-driver.
irvng-wav
commented on August 15, 2024
@ldrahnik thank you for the quick response! How do I git clone a specific commit? or how do I go about using the master branch fixed to the commit you mention?
from asus-numberpad-driver.
ldrahnik
commented on August 15, 2024
@irvng-wav https://www.theserverside.com/blog/Coffee-Talk-Java-News-Stories-and-Opinions/git-clone-specific-commit-id-single-branch-reset-depth-head-main-master
from asus-numberpad-driver.
ldrahnik
commented on August 15, 2024
@irvng-wav Does work for your laptop the previous version or mentioned commit?
from asus-numberpad-driver.
ldrahnik
commented on August 15, 2024
Testing interface i2c-0: failed
Testing interface i2c-2: failed
Unfortunately, It looks like currently the driver does not support your laptop. I found and fixed a bug that allowed you to continue installation with not supported touchpad. In case you are able activate NumberPad on Windows / your laptop has hardware support for NumberPad I need post here your DSDT table using:
$ sudo apt-get install iasl
$ cd <work-dir>
$ sudo cp /sys/firmware/acpi/tables/DSDT DSDT
$ sudo iasl -d DSDT
$ sudo gedit DSDT.dsl # output of this please post here
from asus-numberpad-driver.
irvng-wav
commented on August 15, 2024
Hello @ldrahnik I just successfully installed the 2aae615 commit by following this process:
git clone https://github.com/asus-linux-drivers/asus-numberpad-driver
cd asus-numberpad-driver
git reset --hard 2aae615
bash install.shand I can confirm the numpad is working and it no longer has high CPU usage.
The things I found now is that 1. Launching the calculator isn't working, and 2. The numpad turns on at it's maximum brightness and has too many brightness levels. By default in Windows it only has two levels, a low and a high brightness setting. Having too many is kind of inconvenient.
Here are the logs from /var/log/asus-numberpad-driver for this installation:
error.log
install-04-05-2024-12-16-40.log
from asus-numberpad-driver.
irvng-wav
commented on August 15, 2024
In case you are able activate NumberPad on Windows / your laptop has hardware support for NumberPad I need post here your DSDT table using:
$ sudo apt-get install iasl $ cd <work-dir> $ sudo cp /sys/firmware/acpi/tables/DSDT DSDT $ sudo iasl -d DSDT $ sudo gedit DSDT.dsl # output of this please post here
from asus-numberpad-driver.
irvng-wav
commented on August 15, 2024
The things I found now is that 1. Launching the calculator isn't working
bash /usr/share/asus-numberpad-driver/scripts/calculator_toggle.shWorks correctly, running the command above launches the calculator.
xdotool key XF86CalculatorReturns nothing.
from asus-numberpad-driver.
velito86
commented on August 15, 2024
Hi, recently I have upgraded my Kubuntu to 24.04 and started to experience the same issue. My laptop is Asus Zenbook UX3402VA and previously the numpad was working as expected using Kubuntu 23.10, kernel 6.5.xxx. What I figured so far is that after reboot I have python3 process which makes my laptop to go crazy. After restart of asus_numberpad_driver service, python3 process is not utilizing the CPU and numpad starts working as expected, except that it is turned on to max brightness which is not adjustable (it was adjustable previously).
Desktop
Program version: Release 6.0.0
Distro: Kubuntu 24.04
Kernel: Linux 6.8.0-31
Laptop: Zenbook 14 UX3402VA
DE: Plasma 5.27.11 on X11
from asus-numberpad-driver.
ldrahnik
commented on August 15, 2024
The things I found now is that 1. Launching the calculator isn't working
Confirmed. Fixed (the latest master branch). Please manually check (fix) using dconf-editor (picture below) whether is not missing comma (,) at the start of the path for the shortcut with the calculator toggling script and whether is not missing at the end of previous shortcut too. The next installation the shortcut should be added without any problem.
Wrong:
Correct:
from asus-numberpad-driver.
ldrahnik
commented on August 15, 2024
@velito86 Thank you for reporting.
from asus-numberpad-driver.
ldrahnik
commented on August 15, 2024
By default in Windows it only has two levels
In case you use default config settings of this driver than you set up prefered brightness only once, no? Because than should be used every NumberPad activation recently used brightness. So sounds to me better to have more options for brightness and count 8 does not sound to me be too much.
from asus-numberpad-driver.
irvng-wav
commented on August 15, 2024
Thank you @ldrahnik. I installed the master branch fixed to the commit 66649a9 but then the problematic behavior that I described in the first post returned: numpad didn't work and cpu usage became high.
So uninstalled it and installed it fixed to the commit 2aae615 again, but I edited line 58 of install_calc_toggle.sh by adding the missing apostrophes to the comma so it ended up looking like this:
new_shortcut_string=${filtered_existing_shortcut_string::-2}"', '/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom$NEW_SHORTCUT_INDEX/']"Just like you did in your commit.
Then I rebooted my system, installed dconf-editor, navigated to custom-keybindings, and I found this:
It doesn't look like yours. So I though the calculator toggle was still not working, but then I had the idea to try the toggle when the numpad is on. To my surprise it worked but you have to swipe your finger down from the toggle button and then press the calculator toggle to open the calculator. Here's a video:
IMG_2353.mp4
In Windows you just have to slide your finger down from the toggle button and it automatically launches the calculator plus turns on the numpad, here's a video:
IMG_2354.mp4
At the end of the video you can see a bug when entering a mathematical operation and then trying to close the calculator with the toggle, so even the official driver is kinda wonky lol.
For me it would be ideal if the behavior of the linux driver did that too, that you can use the calculator toggle without the need to have the numpad already on. I don't know if that is something that can be done, if not I'm perfectly pleased with how it works right now! I just edited the activation time to 0.3 and that feels fantastic.
So I want to thank you @ldrahnik! Your work is truly appreciated and also your commitment shows when helping us fix these problems. Thank you for giving us the opportunity of having our computers work with Linux the way they were meant to work. Outstanding job! 😄🙏🏻
from asus-numberpad-driver.
irvng-wav
commented on August 15, 2024
By default in Windows it only has two levels
In case you use default config settings of this driver than you set up prefered brightness only once, no? Because than should be used every NumberPad activation recently used brightness. So sounds to me better to have more options for brightness and count 8 does not sound to me be too much.
Yes! I actually realized that it saves your last brightness level, so that's perfect. Thank you!
from asus-numberpad-driver.
ldrahnik
commented on August 15, 2024
In Windows you just have to slide your finger down from the toggle button and it automatically launches the calculator plus turns on the numpad, here's a video:
I agree, at this moment is necessary to cross over the x axis (changeable in config) but the y axis too (changeable in config too), so both these lines has to crossed. Could you please create a separate issue as feature request? In my mind sounds as best option have something like elipse or similar curve preferred over directly connected points (triangle) which would than serve as threshold line when is slide gesture considered as successful (so I will just check in code whether is point outside of this shape). But depends on performance of mathematics expression for such a shape. Feel free to describe your prefered variant.
from asus-numberpad-driver.
ldrahnik
commented on August 15, 2024
Numpad doesn't work and has high CPU usage
Should be fixed. Tested using X11 only. Can you confirm that? The latest master.
from asus-numberpad-driver.
irvng-wav
commented on August 15, 2024
Numpad doesn't work and has high CPU usage
Should be fixed. Tested using X11 only. Can you confirm that? The latest master.
Can confirm the numpad still doesn't work but it's no longer stressing the CPU. Tested on Wayland and XOrg.
from asus-numberpad-driver.
irvng-wav
commented on August 15, 2024
In Windows you just have to slide your finger down from the toggle button and it automatically launches the calculator plus turns on the numpad, here's a video:
I agree, at this moment is necessary to cross over the x axis (changeable in config) but the y axis too (changeable in config too), so both these lines has to crossed. Could you please create a separate issue as feature request? In my mind sounds as best option have something like elipse or similar curve preferred over directly connected points (triangle) which would than serve as threshold line when is slide gesture considered as successful (so I will just check in code whether is point outside of this shape). But depends on performance of mathematics expression for such a shape. Feel free to describe your prefered variant.
Done. Just opened this feature request.
from asus-numberpad-driver.
ldrahnik
commented on August 15, 2024
@irvng-wav Thank you. I have created separated feature request for change activation area of slide gestures here.
from asus-numberpad-driver.
ldrahnik
commented on August 15, 2024
Numpad doesn't work and has high CPU usage
Should be fixed. Tested using X11 only. Can you confirm that? The latest master.
Can confirm the numpad still doesn't work but it's no longer stressing the CPU. Tested on Wayland and XOrg.
@irvng-wav Does help restarting systemctl service? Then NumberPad works? As was mentioned by @velito86.
from asus-numberpad-driver.
irvng-wav
commented on August 15, 2024
@ldrahnik nope. I tried the following command:
systemctl restart --user [email protected]
and it still doesn't work. In error.log the same thing is logged over and over again:
2024-05-07 02:10:41,108 INFO Detecting keyboard from string: "N: Name="AT Translated Set 2 keyboard""
2024-05-07 02:10:41,108 INFO Set keyboard 4 from H: Handlers=sysrq kbd leds event4
2024-05-07 02:10:41,144 INFO Detecting touchpad from string: "N: Name="ASUE140D:00 04F3:31B9 Touchpad""
2024-05-07 02:10:41,144 INFO Set touchpad device id 15 from S: Sysfs=/devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-15/i2c-ASUE140D:00/0018:04F3:31B9.0001/input/input13
2024-05-07 02:10:41,144 INFO Set touchpad id 10 from H: Handlers=event10 mouse1
2024-05-07 02:10:41,145 INFO Touchpad min-max: x 0-3880, y 0-2299
2024-05-07 02:10:41,145 INFO Numpad min-max: x 200-3680, y 200-2219
2024-05-07 02:10:50,008 INFO Old device at /dev/input/event16 (/sys/devices/virtual/input/input25)
2024-05-07 02:10:50,440 INFO New device at /dev/input/event17 (/sys/devices/virtual/input/input26)
2024-05-07 02:10:51,555 ERROR Listening touchpad events unexpectedly failed
Traceback (most recent call last):
File "/usr/share/asus-numberpad-driver/numberpad.py", line 2355, in <module>
listen_touchpad_events()
File "/usr/share/asus-numberpad-driver/numberpad.py", line 1948, in listen_touchpad_events
for e in d_t.events():
File "/usr/share/asus-numberpad-driver/.env/lib/python3.12/site-packages/libevdev/device.py", line 541, in events
raise EventsDroppedException()
libevdev.device.EventsDroppedException
from asus-numberpad-driver.
ldrahnik
commented on August 15, 2024
@irvng-wav What would help me to figure out what is wrong would move listen_touchpad_events() outside of the try block, try again, and post here error log. Could you do that, please?
now:
try:
listen_touchpad_events()
except:
to:
listen_touchpad_events()
try:
pass
except:
from asus-numberpad-driver.
ldrahnik
commented on August 15, 2024
@irvng-wav The latest commit to the master branch might help too.
from asus-numberpad-driver.
irvng-wav
commented on August 15, 2024
@irvng-wav What would help me to figure out what is wrong would move
listen_touchpad_events()outside of thetryblock, try again, and post here error log. Could you do that, please?now:
try: listen_touchpad_events() except:to:
listen_touchpad_events() try: pass except:
Ok if I understood correctly that would mean editing /usr/share/asus-numberpad-driver/numberpad.py and make it like this:
So I did that, saved the changes and restarted the service with:
systemctl restart --user [email protected]
Now the output of error.log is this:
2024-05-08 00:34:49,632 INFO Detecting keyboard from string: "N: Name="AT Translated Set 2 keyboard""
2024-05-08 00:34:49,632 INFO Set keyboard 4 from H: Handlers=sysrq kbd leds event4
2024-05-08 00:34:49,653 INFO Detecting touchpad from string: "N: Name="ASUE140D:00 04F3:31B9 Touchpad""
2024-05-08 00:34:49,653 INFO Set touchpad device id 15 from S: Sysfs=/devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-15/i2c-ASUE140D:00/0018:04F3:31B9.0001/input/input13
2024-05-08 00:34:49,654 INFO Set touchpad id 10 from H: Handlers=event10 mouse1
2024-05-08 00:34:49,654 INFO Touchpad min-max: x 0-3880, y 0-2299
2024-05-08 00:34:49,654 INFO Numpad min-max: x 200-3680, y 200-2219
2024-05-08 00:34:56,864 INFO Old device at /dev/input/event16 (/sys/devices/virtual/input/input39)
2024-05-08 00:34:57,073 INFO New device at /dev/input/event17 (/sys/devices/virtual/input/input40)
Traceback (most recent call last):
File "/usr/share/asus-numberpad-driver/numberpad.py", line 2353, in <module>
listen_touchpad_events()
File "/usr/share/asus-numberpad-driver/numberpad.py", line 1947, in listen_touchpad_events
for e in d_t.events():
File "/usr/share/asus-numberpad-driver/.env/lib/python3.12/site-packages/libevdev/device.py", line 541, in events
raise EventsDroppedException()
libevdev.device.EventsDroppedException
All this was done with the latest commit 4b75c12.
from asus-numberpad-driver.
ldrahnik
commented on August 15, 2024
@irvng-wav Thank you a lot. Unfortunately I have had no time yet fix this problem. So atleast directly without systemctl installed (https://github.com/asus-linux-drivers/asus-numberpad-driver?tab=readme-ov-file#faq) should driver work, more in #181
from asus-numberpad-driver.
ldrahnik
commented on August 15, 2024
@irvng-wav The latest commits might help too.
from asus-numberpad-driver.
ldrahnik
commented on August 15, 2024
@irvng-wav The latest commit might help too (fixed switching layouts for gnome with older deprecated org.gnome.desktop.input-sources.current - replaced by mru-sources').
from asus-numberpad-driver.
irvng-wav
commented on August 15, 2024
You absolutely did it man! I just installed the latest commit and it works like a charm. Thank you so much for your dedication, commitment and of course your time and energy that you put into this project! I will donate to your ko-fi page as soon as I can. I'm overspent right now so probably when I get my next payment.
I encourage everyone that's benefiting from this project to donate to @ldrahnik. Truly a wonderful service.
Thank you once again. 🙏🏻
Edit: It stopped working again. 😅 I closed my computer and it entered supend mode, then I re-opened it, logged back in and it wasn't working anymore. I rebooted the computer and still wasn't working, then restarted the systemd service and still isn't working. ;-;
Edit 2: Now it suddenly worked again right after I made that last edit. 🤔 Rebooted and it's still working, will update if anything else happens.
Edit 3: Yeah, it randomly stops working. I'm going to revert to the backup that I created with the commit 2aae615 enabled. That one works without any issue. 😜 Still great progress!
from asus-numberpad-driver.
ldrahnik
commented on August 15, 2024
@irvng-wav Could you please post here the entire error log file (/var/log/asus-numberpad-driver/error.log) containing these random stops.
from asus-numberpad-driver.
irvng-wav
commented on August 15, 2024
@irvng-wav Could you please post here the entire error log file (
/var/log/asus-numberpad-driver/error.log) containing these random stops.
Sure! Here's the log from the installation of the last commit d2d8487:
error.log
This time the behavior was this:
- I installed the driver and rebooted, it didn't work for like a minute or two, then it started working, but the backlight level didn't save, so every time I turned off and then on the numpad, the backlight reset to the highest level.
- Then I rebooted, and it also didn't work for like a minute, then it started working and now the backlight level did save.
from asus-numberpad-driver.
ldrahnik
commented on August 15, 2024
2024-05-12 23:27:54,720 ERROR Listening touchpad events unexpectedly failed
Traceback (most recent call last):
File "/usr/share/asus-numberpad-driver/numberpad.py", line 2386, in
udev = dev.create_uinput_device()
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/share/asus-numberpad-driver/.env/lib/python3.12/site-packages/libevdev/device.py", line 764, in create_uinput_device
d._uinput = UinputDevice(self._libevdev, uinput_fd)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/share/asus-numberpad-driver/.env/lib/python3.12/site-packages/libevdev/_clib.py", line 964, in init
raise OSError(-rc, os.strerror(-rc))
PermissionError: [Errno 13] Permission denied
What is the output of $ groups?
from asus-numberpad-driver.
ldrahnik
commented on August 15, 2024
@irvng-wav Please, try to run driver directly without systemctl service using $ /usr/share/asus-numberpad-driver/.env/bin/python3 /usr/share/asus-numberpad-driver/numberpad.py <up5401ea|e210ma|..>. Does it work? Clean the error log file before and post it here please.
from asus-numberpad-driver.
irvng-wav
commented on August 15, 2024
@irvng-wav Please, try to run driver directly without systemctl service using
$ /usr/share/asus-numberpad-driver/.env/bin/python3 /usr/share/asus-numberpad-driver/numberpad.py <up5401ea|e210ma|..>. Does it work? Clean the error log file before and post it here please.
I get this (the numpad was already working before I launched the command):
[irvng@arch-zenbook ~]$ /usr/share/asus-numberpad-driver/.env/bin/python3 /usr/share/asus-numberpad-driver/numberpad.py up5401ea
2024-05-17 00:07:10,816 INFO Detecting keyboard from string: "N: Name="AT Translated Set 2 keyboard""
2024-05-17 00:07:10,817 INFO Set keyboard 4 from H: Handlers=sysrq kbd leds event4
2024-05-17 00:07:10,846 INFO Detecting touchpad from string: "N: Name="ASUE140D:00 04F3:31B9 Touchpad""
2024-05-17 00:07:10,846 INFO Set touchpad device id 15 from S: Sysfs=/devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-15/i2c-ASUE140D:00/0018:04F3:31B9.0001/input/input13
2024-05-17 00:07:10,846 INFO Set touchpad id 10 from H: Handlers=event10 mouse1
2024-05-17 00:07:10,846 INFO Touchpad min-max: x 0-3880, y 0-2299
2024-05-17 00:07:10,846 INFO Numpad min-max: x 200-3680, y 200-2219
2024-05-17 00:07:18,941 INFO Setting up for config file key: "brightness" with value: "0x48"
2024-05-17 00:07:19,046 ERROR Listening touchpad events unexpectedly failed
Traceback (most recent call last):
File "/usr/share/asus-numberpad-driver/numberpad.py", line 2435, in <module>
listen_touchpad_events()
File "/usr/share/asus-numberpad-driver/numberpad.py", line 1957, in listen_touchpad_events
for e in d_t.events():
File "/usr/share/asus-numberpad-driver/.env/lib/python3.12/site-packages/libevdev/device.py", line 541, in events
raise EventsDroppedException()
libevdev.device.EventsDroppedException
2024-05-17 00:07:19,048 INFO Clean up started
[2024-05-17 00:07:19,092 pyinotify ERROR] Cannot delete unknown watch descriptor '/home/irvng'
2024-05-17 00:07:19,092 ERROR Cannot delete unknown watch descriptor '/home/irvng'
2024-05-17 00:07:19,093 INFO Clean up finished
2024-05-17 00:07:19,093 INFO Exiting
from asus-numberpad-driver.
irvng-wav
commented on August 15, 2024
After my last comment I deleted error.log to start fresh again, rebooted the computer and did the same thing. Now the output of /usr/share/asus-numberpad-driver/.env/bin/python3 /usr/share/asus-numberpad-driver/numberpad.py up5401ea is this:
[irvng@arch-zenbook ~]$ /usr/share/asus-numberpad-driver/.env/bin/python3 /usr/share/asus-numberpad-driver/numberpad.py up5401ea
2024-05-17 00:11:21,452 INFO Detecting keyboard from string: "N: Name="AT Translated Set 2 keyboard""
2024-05-17 00:11:21,452 INFO Set keyboard 4 from H: Handlers=sysrq kbd leds event4
2024-05-17 00:11:21,483 INFO Detecting touchpad from string: "N: Name="ASUE140D:00 04F3:31B9 Touchpad""
2024-05-17 00:11:21,483 INFO Set touchpad device id 15 from S: Sysfs=/devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-15/i2c-ASUE140D:00/0018:04F3:31B9.0001/input/input13
2024-05-17 00:11:21,483 INFO Set touchpad id 10 from H: Handlers=event10 mouse1
2024-05-17 00:11:21,483 INFO Touchpad min-max: x 0-3880, y 0-2299
2024-05-17 00:11:21,483 INFO Numpad min-max: x 200-3680, y 200-2219
2024-05-17 00:11:52,020 INFO Touched top_right_icon area (numlock) in time: 1715926312.0209637
2024-05-17 00:11:52,480 INFO Un-touched top_right_icon area (representing numlock key) in time: 1715926312.480498
WARNING: running xinput against an Xwayland server. See the xinput man page for details.
unable to find device ASUE140D:00 04F3:31B9 Touchpad
2024-05-17 00:11:52,576 INFO Setting up for config file key: "enabled" with value: "True"
2024-05-17 00:11:52,577 INFO check_config_values_changes: detected internal change of config file -> do nothing -> would be deadlock
<Event dir=False mask=0x8 maskname=IN_CLOSE_WRITE name=numberpad_dev path=/home/irvng pathname=/home/irvng/numberpad_dev wd=1 >
2024-05-17 00:11:52,677 INFO Numpad activated
2024-05-17 00:11:54,593 INFO Touched top_right_icon area (numlock) in time: 1715926314.593668
2024-05-17 00:11:55,185 INFO Un-touched top_right_icon area (representing numlock key) in time: 1715926315.185171
WARNING: running xinput against an Xwayland server. See the xinput man page for details.
unable to find device ASUE140D:00 04F3:31B9 Touchpad
2024-05-17 00:11:55,290 INFO Setting up for config file key: "enabled" with value: "False"
2024-05-17 00:11:55,291 INFO check_config_values_changes: detected internal change of config file -> do nothing -> would be deadlock
<Event dir=False mask=0x8 maskname=IN_CLOSE_WRITE name=numberpad_dev path=/home/irvng pathname=/home/irvng/numberpad_dev wd=1 >
2024-05-17 00:11:55,391 INFO Numpad deactivated
2024-05-17 00:12:00,986 INFO Touched top_right_icon area (numlock) in time: 1715926320.9868817
2024-05-17 00:12:01,543 INFO Un-touched top_right_icon area (representing numlock key) in time: 1715926321.5433066
WARNING: running xinput against an Xwayland server. See the xinput man page for details.
unable to find device ASUE140D:00 04F3:31B9 Touchpad
2024-05-17 00:12:01,639 INFO Setting up for config file key: "enabled" with value: "True"
2024-05-17 00:12:01,639 INFO check_config_values_changes: detected internal change of config file -> do nothing -> would be deadlock
<Event dir=False mask=0x8 maskname=IN_CLOSE_WRITE name=numberpad_dev path=/home/irvng pathname=/home/irvng/numberpad_dev wd=1 >
2024-05-17 00:12:01,739 INFO Numpad activated
2024-05-17 00:12:02,699 INFO Touched top_right_icon area (numlock) in time: 1715926322.6990178
2024-05-17 00:12:03,149 INFO Un-touched top_right_icon area (representing numlock key) in time: 1715926323.1490846
WARNING: running xinput against an Xwayland server. See the xinput man page for details.
unable to find device ASUE140D:00 04F3:31B9 Touchpad
2024-05-17 00:12:03,337 INFO Setting up for config file key: "enabled" with value: "False"
2024-05-17 00:12:03,337 INFO check_config_values_changes: detected internal change of config file -> do nothing -> would be deadlock
<Event dir=False mask=0x8 maskname=IN_CLOSE_WRITE name=numberpad_dev path=/home/irvng pathname=/home/irvng/numberpad_dev wd=1 >
2024-05-17 00:12:03,432 INFO Touched top_right_icon area (numlock) in time: 1715926323.4329174
2024-05-17 00:12:03,437 INFO Numpad deactivated
2024-05-17 00:12:03,647 INFO Un-touched top_right_icon area (representing numlock key) in time: 1715926323.6470108
2024-05-17 00:12:03,958 INFO Touched top_right_icon area (numlock) in time: 1715926323.958899
WARNING: running xinput against an Xwayland server. See the xinput man page for details.
unable to find device ASUE140D:00 04F3:31B9 Touchpad
2024-05-17 00:12:04,499 INFO Setting up for config file key: "enabled" with value: "True"
2024-05-17 00:12:04,499 INFO check_config_values_changes: detected internal change of config file -> do nothing -> would be deadlock
<Event dir=False mask=0x8 maskname=IN_CLOSE_WRITE name=numberpad_dev path=/home/irvng pathname=/home/irvng/numberpad_dev wd=1 >
2024-05-17 00:12:04,511 INFO Un-touched top_right_icon area (representing numlock key) in time: 1715926324.5117722
2024-05-17 00:12:04,599 INFO Numpad activated
2024-05-17 00:12:05,661 INFO Touched top_right_icon area (numlock) in time: 1715926325.6613195
WARNING: running xinput against an Xwayland server. See the xinput man page for details.
unable to find device ASUE140D:00 04F3:31B9 Touchpad
2024-05-17 00:12:06,167 INFO Setting up for config file key: "enabled" with value: "False"
2024-05-17 00:12:06,167 INFO check_config_values_changes: detected internal change of config file -> do nothing -> would be deadlock
<Event dir=False mask=0x8 maskname=IN_CLOSE_WRITE name=numberpad_dev path=/home/irvng pathname=/home/irvng/numberpad_dev wd=1 >
2024-05-17 00:12:06,268 INFO Numpad deactivated
2024-05-17 00:12:06,345 INFO Un-touched top_right_icon area (representing numlock key) in time: 1715926326.3456397
The numpad was also working before I entered the command. I think because of that now the numpad first turns on to the lowest brightness (I left it there), then it changes to max brightness. Also when I change it back to the lowest brightness it doesn't save the state. Here's an updated error.log after that behavior:
from asus-numberpad-driver.
ldrahnik
commented on August 15, 2024
@irvng-wav What is the output of $ groups?
from asus-numberpad-driver.
irvng-wav
commented on August 15, 2024
Once again, deleted error.log, rebooted, but this time I ran systemctl stop --user [email protected] to stop the already running numpad and then entered /usr/share/asus-numberpad-driver/.env/bin/python3 /usr/share/asus-numberpad-driver/numberpad.py up5401ea:
[irvng@arch-zenbook ~]$ /usr/share/asus-numberpad-driver/.env/bin/python3 /usr/share/asus-numberpad-driver/numberpad.py up5401ea
2024-05-17 00:20:49,221 INFO Detecting keyboard from string: "N: Name="AT Translated Set 2 keyboard""
2024-05-17 00:20:49,221 INFO Set keyboard 4 from H: Handlers=sysrq kbd leds event4
2024-05-17 00:20:49,256 INFO Detecting touchpad from string: "N: Name="ASUE140D:00 04F3:31B9 Touchpad""
2024-05-17 00:20:49,256 INFO Set touchpad device id 15 from S: Sysfs=/devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-15/i2c-ASUE140D:00/0018:04F3:31B9.0001/input/input13
2024-05-17 00:20:49,256 INFO Set touchpad id 9 from H: Handlers=event9 mouse1
2024-05-17 00:20:49,256 INFO Touchpad min-max: x 0-3880, y 0-2299
2024-05-17 00:20:49,256 INFO Numpad min-max: x 200-3680, y 200-2219
2024-05-17 00:21:04,666 INFO Touched top_right_icon area (numlock) in time: 1715926864.666638
2024-05-17 00:21:05,673 INFO The numpad numlock was pressed longer than the activation time and will be activated: 1.0063786506652832
2024-05-17 00:21:05,673 INFO Activation time: 1.0
2024-05-17 00:21:05,713 INFO System numlock activated
2024-05-17 00:21:05,713 INFO Numpad activated
WARNING: running xinput against an Xwayland server. See the xinput man page for details.
unable to find device ASUE140D:00 04F3:31B9 Touchpad
2024-05-17 00:21:05,731 INFO Setting up for config file key: "enabled" with value: "True"
2024-05-17 00:21:05,731 INFO check_config_values_changes: detected internal change of config file -> do nothing -> would be deadlock
<Event dir=False mask=0x8 maskname=IN_CLOSE_WRITE name=numberpad_dev path=/home/irvng pathname=/home/irvng/numberpad_dev wd=1 >
2024-05-17 00:21:06,143 INFO Un-touched top_right_icon area (representing numlock key) in time: 1715926866.143782
2024-05-17 00:21:08,666 INFO Touched top_right_icon area (numlock) in time: 1715926868.6663475
2024-05-17 00:21:09,672 INFO The numpad numlock was pressed longer than the activation time and will be activated: 1.0062620639801025
2024-05-17 00:21:09,672 INFO Activation time: 1.0
2024-05-17 00:21:09,699 INFO System numlock deactivated
2024-05-17 00:21:09,700 INFO Numpad deactivated
WARNING: running xinput against an Xwayland server. See the xinput man page for details.
unable to find device ASUE140D:00 04F3:31B9 Touchpad
2024-05-17 00:21:09,722 INFO Setting up for config file key: "enabled" with value: "False"
2024-05-17 00:21:09,723 INFO check_config_values_changes: detected internal change of config file -> do nothing -> would be deadlock
<Event dir=False mask=0x8 maskname=IN_CLOSE_WRITE name=numberpad_dev path=/home/irvng pathname=/home/irvng/numberpad_dev wd=1 >
2024-05-17 00:21:10,053 INFO Un-touched top_right_icon area (representing numlock key) in time: 1715926870.0538008
2024-05-17 00:21:10,213 INFO Touched top_right_icon area (numlock) in time: 1715926870.212999
2024-05-17 00:21:11,216 INFO The numpad numlock was pressed longer than the activation time and will be activated: 1.0030953884124756
2024-05-17 00:21:11,216 INFO Activation time: 1.0
2024-05-17 00:21:11,236 INFO System numlock activated
2024-05-17 00:21:11,236 INFO Numpad activated
WARNING: running xinput against an Xwayland server. See the xinput man page for details.
unable to find device ASUE140D:00 04F3:31B9 Touchpad
2024-05-17 00:21:11,256 INFO Setting up for config file key: "enabled" with value: "True"
2024-05-17 00:21:11,256 INFO check_config_values_changes: detected internal change of config file -> do nothing -> would be deadlock
<Event dir=False mask=0x8 maskname=IN_CLOSE_WRITE name=numberpad_dev path=/home/irvng pathname=/home/irvng/numberpad_dev wd=1 >
2024-05-17 00:21:11,562 INFO Un-touched top_right_icon area (representing numlock key) in time: 1715926871.5622182
2024-05-17 00:21:12,040 INFO Touched top_left_icon area in time: 1715926872.0401757
2024-05-17 00:21:12,531 INFO Slide from top_left_icon exceeded the activation threshold for x and y.
2024-05-17 00:21:12,531 INFO Activation x 3830.00 (top left corner is 0; required > 776.00 / 3880.00)
2024-05-17 00:21:12,531 INFO Activation y 804.00 (top left corner is 0; required > 459.80 / 2299.00)
2024-05-17 00:21:12,531 INFO Used bindings for touchpad left_icon slide function
2024-05-17 00:21:12,531 INFO Touched top_left_icon area in time: 1715926872.5315113
2024-05-17 00:21:13,285 INFO Un-touched top_right_icon area (representing numlock key) in time: 1715926873.2852216
2024-05-17 00:21:14,088 INFO Touched top_left_icon area in time: 1715926874.0885785
2024-05-17 00:21:14,482 INFO Slide from top_left_icon exceeded the activation threshold for x and y.
2024-05-17 00:21:14,482 INFO Activation x 3852.00 (top left corner is 0; required > 776.00 / 3880.00)
2024-05-17 00:21:14,482 INFO Activation y 729.00 (top left corner is 0; required > 459.80 / 2299.00)
2024-05-17 00:21:14,482 INFO Used bindings for touchpad left_icon slide function
2024-05-17 00:21:14,483 INFO Touched top_left_icon area in time: 1715926874.4830256
2024-05-17 00:21:15,008 INFO Un-touched top_right_icon area (representing numlock key) in time: 1715926875.0086925
2024-05-17 00:21:17,773 INFO Touched top_right_icon area (numlock) in time: 1715926877.7733996
2024-05-17 00:21:18,780 INFO The numpad numlock was pressed longer than the activation time and will be activated: 1.0065786838531494
2024-05-17 00:21:18,780 INFO Activation time: 1.0
2024-05-17 00:21:18,806 INFO System numlock deactivated
2024-05-17 00:21:18,806 INFO Numpad deactivated
WARNING: running xinput against an Xwayland server. See the xinput man page for details.
unable to find device ASUE140D:00 04F3:31B9 Touchpad
2024-05-17 00:21:18,825 INFO Setting up for config file key: "enabled" with value: "False"
2024-05-17 00:21:18,825 INFO check_config_values_changes: detected internal change of config file -> do nothing -> would be deadlock
<Event dir=False mask=0x8 maskname=IN_CLOSE_WRITE name=numberpad_dev path=/home/irvng pathname=/home/irvng/numberpad_dev wd=1 >
2024-05-17 00:21:19,098 INFO Un-touched top_right_icon area (representing numlock key) in time: 1715926879.0985138
2024-05-17 00:21:20,527 INFO Touched top_right_icon area (numlock) in time: 1715926880.5277302
2024-05-17 00:21:21,533 INFO The numpad numlock was pressed longer than the activation time and will be activated: 1.0061426162719727
2024-05-17 00:21:21,534 INFO Activation time: 1.0
2024-05-17 00:21:21,566 INFO System numlock activated
2024-05-17 00:21:21,566 INFO Numpad activated
WARNING: running xinput against an Xwayland server. See the xinput man page for details.
unable to find device ASUE140D:00 04F3:31B9 Touchpad
2024-05-17 00:21:21,615 INFO Setting up for config file key: "enabled" with value: "True"
2024-05-17 00:21:21,616 INFO check_config_values_changes: detected internal change of config file -> do nothing -> would be deadlock
<Event dir=False mask=0x8 maskname=IN_CLOSE_WRITE name=numberpad_dev path=/home/irvng pathname=/home/irvng/numberpad_dev wd=1 >
2024-05-17 00:21:21,845 INFO Un-touched top_right_icon area (representing numlock key) in time: 1715926881.8458657
2024-05-17 00:21:21,977 INFO Touched top_left_icon area in time: 1715926881.9771125
2024-05-17 00:21:22,980 INFO The top_left_icon was pressed longer than the activation time: 1.0031287670135498
2024-05-17 00:21:22,980 INFO Activation time: 1.0
2024-05-17 00:21:22,980 INFO Increased brightness of backlight to
2024-05-17 00:21:22,980 INFO 0
2024-05-17 00:21:22,980 INFO Setting up for config file key: "brightness" with value: "0x41"
2024-05-17 00:21:22,980 INFO check_config_values_changes: detected internal change of config file -> do nothing -> would be deadlock
<Event dir=False mask=0x8 maskname=IN_CLOSE_WRITE name=numberpad_dev path=/home/irvng pathname=/home/irvng/numberpad_dev wd=1 >
2024-05-17 00:21:23,361 INFO Un-touched top_left_icon area in time: 1715926883.3612576
2024-05-17 00:21:23,513 INFO Touched top_right_icon area (numlock) in time: 1715926883.5137894
2024-05-17 00:21:24,516 INFO The numpad numlock was pressed longer than the activation time and will be activated: 1.002772569656372
2024-05-17 00:21:24,516 INFO Activation time: 1.0
2024-05-17 00:21:24,539 INFO System numlock deactivated
2024-05-17 00:21:24,539 INFO Numpad deactivated
WARNING: running xinput against an Xwayland server. See the xinput man page for details.
unable to find device ASUE140D:00 04F3:31B9 Touchpad
2024-05-17 00:21:24,558 INFO Setting up for config file key: "enabled" with value: "False"
2024-05-17 00:21:24,559 INFO check_config_values_changes: detected internal change of config file -> do nothing -> would be deadlock
<Event dir=False mask=0x8 maskname=IN_CLOSE_WRITE name=numberpad_dev path=/home/irvng pathname=/home/irvng/numberpad_dev wd=1 >
2024-05-17 00:21:24,841 INFO Un-touched top_right_icon area (representing numlock key) in time: 1715926884.8419502
2024-05-17 00:21:25,277 INFO Touched top_right_icon area (numlock) in time: 1715926885.277892
2024-05-17 00:21:26,281 INFO The numpad numlock was pressed longer than the activation time and will be activated: 1.0032830238342285
2024-05-17 00:21:26,281 INFO Activation time: 1.0
2024-05-17 00:21:26,316 INFO System numlock activated
2024-05-17 00:21:26,316 INFO Numpad activated
WARNING: running xinput against an Xwayland server. See the xinput man page for details.
unable to find device ASUE140D:00 04F3:31B9 Touchpad
2024-05-17 00:21:26,337 INFO Setting up for config file key: "enabled" with value: "True"
2024-05-17 00:21:26,338 INFO check_config_values_changes: detected internal change of config file -> do nothing -> would be deadlock
<Event dir=False mask=0x8 maskname=IN_CLOSE_WRITE name=numberpad_dev path=/home/irvng pathname=/home/irvng/numberpad_dev wd=1 >
2024-05-17 00:21:26,703 INFO Un-touched top_right_icon area (representing numlock key) in time: 1715926886.7033303
2024-05-17 00:21:27,852 INFO Touched top_right_icon area (numlock) in time: 1715926887.8525546
2024-05-17 00:21:28,731 INFO Un-touched top_right_icon area (representing numlock key) in time: 1715926888.7310424
2024-05-17 00:21:29,305 INFO Touched top_right_icon area (numlock) in time: 1715926889.3055847
2024-05-17 00:21:30,308 INFO The numpad numlock was pressed longer than the activation time and will be activated: 1.0029537677764893
2024-05-17 00:21:30,308 INFO Activation time: 1.0
2024-05-17 00:21:30,339 INFO System numlock deactivated
2024-05-17 00:21:30,339 INFO Numpad deactivated
WARNING: running xinput against an Xwayland server. See the xinput man page for details.
unable to find device ASUE140D:00 04F3:31B9 Touchpad
2024-05-17 00:21:30,361 INFO Setting up for config file key: "enabled" with value: "False"
2024-05-17 00:21:30,362 INFO check_config_values_changes: detected internal change of config file -> do nothing -> would be deadlock
<Event dir=False mask=0x8 maskname=IN_CLOSE_WRITE name=numberpad_dev path=/home/irvng pathname=/home/irvng/numberpad_dev wd=1 >
2024-05-17 00:21:30,509 INFO Un-touched top_right_icon area (representing numlock key) in time: 1715926890.5096023
Here's the error.log corresponding to that:
error.log
from asus-numberpad-driver.
irvng-wav
commented on August 15, 2024
@irvng-wav What is the output of
$ groups?
[irvng@arch-zenbook ~]$ groups
i2c realtime video input audio wheel irvng numberpad uinput
from asus-numberpad-driver.
ldrahnik
commented on August 15, 2024
@irvng-wav Also when I change it back to the lowest brightness it doesn't save the state.
Please check rights of parent directory in config file location & config file.
$ usr/share/asus-numberpad-driver$ ls -la
total 124
drwxr-xr-x 6 ldrahnik root 4096 May 17 18:12 .
drwxr-xr-x 312 root root 12288 May 5 16:59 ..
drwxrwxr-x 4 ldrahnik ldrahnik 4096 May 5 16:59 .env
drwxr-xr-x 3 ldrahnik root 4096 May 17 18:07 layouts
-rw-rw-r-- 1 ldrahnik ldrahnik 715 May 17 18:18 numberpad_dev
-rwxr-xr-x 1 root root 86973 May 17 18:07 numberpad.py
drwxr-xr-x 2 ldrahnik root 4096 May 5 16:59 scripts
drwxr-xr-x 2 ldrahnik root 4096 May 5 17:00 udev
Lowest saved brightness looks like 0x41 (should be changed each 1s during the time when you hold the top left icon spot):
cat numberpad_dev
[main]
numpad_disables_sys_numlock = 1
disable_due_inactivity_time = 0
touchpad_disables_numpad = 1
key_repetitions = 0
multitouch = 0
one_touch_key_rotation = 0
activation_time = 1
sys_numlock_enables_numpad = 1
top_left_icon_activation_time = 1
top_left_icon_slide_func_activation_x_ratio = 0.2
top_left_icon_slide_func_activation_y_ratio = 0.2
top_right_icon_slide_func_activation_x_ratio = 0.2
top_right_icon_slide_func_activation_y_ratio = 0.2
enabled_touchpad_pointer = 3
press_key_when_is_done_untouch = 1
enabled = 0
default_backlight_level = 0x01
brightness = 0x41
top_left_icon_brightness_func_disabled = 0
distance_to_move_only_pointer = 0
idled = 0
idle_brightness = 30
idle_enabled = 1
idle_time = 10
Does it change? Thank you for your time. It looks like the problem is only Arch.
from asus-numberpad-driver.
irvng-wav
commented on August 15, 2024
Please check rights of parent directory in config file location & config file.
[irvng@arch-zenbook asus-numberpad-driver]$ ls -la
total 124
drwxr-xr-x 6 irvng root 4096 may 17 13:18 .
drwxr-xr-x 239 root root 12288 may 17 00:01 ..
drwxr-xr-x 4 irvng irvng 4096 may 17 00:01 .env
drwxr-xr-x 3 irvng root 4096 may 17 00:02 layouts
-rw-r--r-- 1 irvng irvng 719 may 17 13:20 numberpad_dev
-rwxr-xr-x 1 root root 86973 may 17 00:01 numberpad.py
drwxr-xr-x 2 root root 4096 may 17 00:02 scripts
drwxr-xr-x 2 root root 4096 may 17 00:02 udev
from asus-numberpad-driver.
irvng-wav
commented on August 15, 2024
I restarted my computer a couple times and the numpad wasn't working, although the service was running. The first time the systemctl service displayed an error but I don't have that log anymore, on the second reboot the status was active and running without any problems.
So I started manually the service with
/usr/share/asus-numberpad-driver/.env/bin/python3 /usr/share/asus-numberpad-driver/numberpad.py up5401ea
Lowest saved brightness looks like
0x41(should be changed each 1s during the time when you hold the top left icon spot):
Does it change? Thank you for your time. It looks like the problem is only Arch.
You're welcome! Thank you as well. Here's a video:
IMG_2388.1._compressed.mp4
The file numberpad_dev has read and write permissions, and the changes are successfully written to it, but even then the numpad still reverts back to max brightness. Weird behavior man. The commit 2aae615 works for me perfectly. Literally no issues at all. What's different from that version compared to this one?
from asus-numberpad-driver.
ldrahnik
commented on August 15, 2024
@irvng-wav About not receiving keymap through wayland - I have added debug logs to the master branch. Please, start the driver directly with LOG=DEBUG .. at the start and post printed output to the terminal here.
You should see something like this (Fedora with sway in virtualbox):
2024-05-18 17:07:28,339 INFO Detecting keyboard from string: "N: Name="AT Translated Set 2 keyboard""
2024-05-18 17:07:28,340 INFO Set keyboard 2 from H: Handlers=sysrq kbd leds event2
2024-05-18 17:07:28,375 INFO Detecting touchpad from string: "N: Name="VirtualBox USB Tablet""
2024-05-18 17:07:28,378 INFO Set touchpad device id S: Sysfs=/devices/pci0000:00/0000:00:06.0/usb1/1-1/1-1:1.0/0003:80EE:0021.0001/input/input5 from S: Sysfs=/devices/pci0000:00/0000:00:06.0/usb1/1-1/1-1:1.0/0003:80EE:0021.0001/input/input5
2024-05-18 17:07:28,385 INFO Set touchpad id 4 from H: Handlers=mouse1 event4 js0
2024-05-18 17:07:28,387 ERROR Can't open the I2C bus connection (id: S: Sysfs=/devices/pci0000:00/0000:00:06.0/usb1/1-1/1-1:1.0/0003:80EE:0021.0001/input/input5)
2024-05-18 17:07:28,390 INFO Touchpad min-max: x 0-32767, y 0-32767
2024-05-18 17:07:28,390 INFO Numpad min-max: x 200-32567, y 200-32687
2024-05-18 17:07:28,478 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7fab474b63c0>
2024-05-18 17:07:28,478 DEBUG 1
2024-05-18 17:07:28,478 DEBUG wl_shm
2024-05-18 17:07:28,478 DEBUG 1
2024-05-18 17:07:28,478 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7fab474b63c0>
2024-05-18 17:07:28,479 DEBUG 2
2024-05-18 17:07:28,479 DEBUG wl_drm
2024-05-18 17:07:28,479 DEBUG 2
2024-05-18 17:07:28,479 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7fab474b63c0>
2024-05-18 17:07:28,479 DEBUG 3
2024-05-18 17:07:28,479 DEBUG zwp_linux_dmabuf_v1
2024-05-18 17:07:28,479 DEBUG 4
2024-05-18 17:07:28,479 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7fab474b63c0>
2024-05-18 17:07:28,479 DEBUG 4
2024-05-18 17:07:28,479 DEBUG wl_compositor
2024-05-18 17:07:28,479 DEBUG 5
2024-05-18 17:07:28,479 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7fab474b63c0>
2024-05-18 17:07:28,480 DEBUG 5
2024-05-18 17:07:28,480 DEBUG wl_subcompositor
2024-05-18 17:07:28,480 DEBUG 1
2024-05-18 17:07:28,480 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7fab474b63c0>
2024-05-18 17:07:28,480 DEBUG 6
2024-05-18 17:07:28,480 DEBUG wl_data_device_manager
2024-05-18 17:07:28,480 DEBUG 3
2024-05-18 17:07:28,480 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7fab474b63c0>
2024-05-18 17:07:28,480 DEBUG 7
2024-05-18 17:07:28,480 DEBUG zwlr_gamma_control_manager_v1
2024-05-18 17:07:28,480 DEBUG 1
2024-05-18 17:07:28,486 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7fab474b63c0>
2024-05-18 17:07:28,486 DEBUG 8
2024-05-18 17:07:28,486 DEBUG zxdg_output_manager_v1
2024-05-18 17:07:28,486 DEBUG 3
2024-05-18 17:07:28,486 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7fab474b63c0>
2024-05-18 17:07:28,486 DEBUG 9
2024-05-18 17:07:28,486 DEBUG org_kde_kwin_idle
2024-05-18 17:07:28,486 DEBUG 1
2024-05-18 17:07:28,486 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7fab474b63c0>
2024-05-18 17:07:28,486 DEBUG 10
2024-05-18 17:07:28,486 DEBUG ext_idle_notifier_v1
2024-05-18 17:07:28,486 DEBUG 1
2024-05-18 17:07:28,487 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7fab474b63c0>
2024-05-18 17:07:28,487 DEBUG 11
2024-05-18 17:07:28,487 DEBUG zwp_idle_inhibit_manager_v1
2024-05-18 17:07:28,487 DEBUG 1
2024-05-18 17:07:28,487 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7fab474b63c0>
2024-05-18 17:07:28,487 DEBUG 12
2024-05-18 17:07:28,487 DEBUG zwlr_layer_shell_v1
2024-05-18 17:07:28,487 DEBUG 4
2024-05-18 17:07:28,487 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7fab474b63c0>
2024-05-18 17:07:28,487 DEBUG 13
2024-05-18 17:07:28,487 DEBUG xdg_wm_base
2024-05-18 17:07:28,487 DEBUG 2
2024-05-18 17:07:28,488 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7fab474b63c0>
2024-05-18 17:07:28,488 DEBUG 14
2024-05-18 17:07:28,488 DEBUG zwp_tablet_manager_v2
2024-05-18 17:07:28,488 DEBUG 1
2024-05-18 17:07:28,488 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7fab474b63c0>
2024-05-18 17:07:28,488 DEBUG 15
2024-05-18 17:07:28,488 DEBUG org_kde_kwin_server_decoration_manager
2024-05-18 17:07:28,488 DEBUG 1
2024-05-18 17:07:28,488 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7fab474b63c0>
2024-05-18 17:07:28,488 DEBUG 16
2024-05-18 17:07:28,488 DEBUG zxdg_decoration_manager_v1
2024-05-18 17:07:28,488 DEBUG 1
2024-05-18 17:07:28,489 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7fab474b63c0>
2024-05-18 17:07:28,489 DEBUG 17
2024-05-18 17:07:28,489 DEBUG zwp_relative_pointer_manager_v1
2024-05-18 17:07:28,489 DEBUG 1
2024-05-18 17:07:28,489 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7fab474b63c0>
2024-05-18 17:07:28,489 DEBUG 18
2024-05-18 17:07:28,489 DEBUG zwp_pointer_constraints_v1
2024-05-18 17:07:28,489 DEBUG 1
2024-05-18 17:07:28,489 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7fab474b63c0>
2024-05-18 17:07:28,489 DEBUG 19
2024-05-18 17:07:28,489 DEBUG wp_presentation
2024-05-18 17:07:28,489 DEBUG 1
2024-05-18 17:07:28,490 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7fab474b63c0>
2024-05-18 17:07:28,490 DEBUG 20
2024-05-18 17:07:28,490 DEBUG zwlr_output_manager_v1
2024-05-18 17:07:28,490 DEBUG 4
2024-05-18 17:07:28,490 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7fab474b63c0>
2024-05-18 17:07:28,490 DEBUG 21
2024-05-18 17:07:28,490 DEBUG zwlr_output_power_manager_v1
2024-05-18 17:07:28,490 DEBUG 1
2024-05-18 17:07:28,490 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7fab474b63c0>
2024-05-18 17:07:28,490 DEBUG 22
2024-05-18 17:07:28,490 DEBUG zwp_input_method_manager_v2
2024-05-18 17:07:28,494 DEBUG 1
2024-05-18 17:07:28,494 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7fab474b63c0>
2024-05-18 17:07:28,494 DEBUG 23
2024-05-18 17:07:28,494 DEBUG zwp_text_input_manager_v3
2024-05-18 17:07:28,494 DEBUG 1
2024-05-18 17:07:28,494 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7fab474b63c0>
2024-05-18 17:07:28,514 DEBUG 24
2024-05-18 17:07:28,514 DEBUG zwlr_foreign_toplevel_manager_v1
2024-05-18 17:07:28,514 DEBUG 3
2024-05-18 17:07:28,514 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7fab474b63c0>
2024-05-18 17:07:28,514 DEBUG 25
2024-05-18 17:07:28,514 DEBUG ext_session_lock_manager_v1
2024-05-18 17:07:28,514 DEBUG 1
2024-05-18 17:07:28,514 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7fab474b63c0>
2024-05-18 17:07:28,514 DEBUG 26
2024-05-18 17:07:28,515 DEBUG wp_drm_lease_device_v1
2024-05-18 17:07:28,515 DEBUG 1
2024-05-18 17:07:28,515 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7fab474b63c0>
2024-05-18 17:07:28,515 DEBUG 27
2024-05-18 17:07:28,515 DEBUG zwlr_export_dmabuf_manager_v1
2024-05-18 17:07:28,515 DEBUG 1
2024-05-18 17:07:28,515 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7fab474b63c0>
2024-05-18 17:07:28,515 DEBUG 28
2024-05-18 17:07:28,515 DEBUG zwlr_screencopy_manager_v1
2024-05-18 17:07:28,515 DEBUG 3
2024-05-18 17:07:28,516 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7fab474b63c0>
2024-05-18 17:07:28,516 DEBUG 29
2024-05-18 17:07:28,516 DEBUG zwlr_data_control_manager_v1
2024-05-18 17:07:28,516 DEBUG 2
2024-05-18 17:07:28,516 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7fab474b63c0>
2024-05-18 17:07:28,516 DEBUG 30
2024-05-18 17:07:28,516 DEBUG zwp_primary_selection_device_manager_v1
2024-05-18 17:07:28,516 DEBUG 1
2024-05-18 17:07:28,516 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7fab474b63c0>
2024-05-18 17:07:28,516 DEBUG 31
2024-05-18 17:07:28,516 DEBUG wp_viewporter
2024-05-18 17:07:28,516 DEBUG 1
2024-05-18 17:07:28,517 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7fab474b63c0>
2024-05-18 17:07:28,517 DEBUG 32
2024-05-18 17:07:28,517 DEBUG wp_single_pixel_buffer_manager_v1
2024-05-18 17:07:28,517 DEBUG 1
2024-05-18 17:07:28,517 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7fab474b63c0>
2024-05-18 17:07:28,517 DEBUG 33
2024-05-18 17:07:28,517 DEBUG zxdg_exporter_v1
2024-05-18 17:07:28,517 DEBUG 1
2024-05-18 17:07:28,517 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7fab474b63c0>
2024-05-18 17:07:28,517 DEBUG 34
2024-05-18 17:07:28,517 DEBUG zxdg_importer_v1
2024-05-18 17:07:28,517 DEBUG 1
2024-05-18 17:07:28,517 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7fab474b63c0>
2024-05-18 17:07:28,518 DEBUG 35
2024-05-18 17:07:28,518 DEBUG zxdg_exporter_v2
2024-05-18 17:07:28,518 DEBUG 1
2024-05-18 17:07:28,518 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7fab474b63c0>
2024-05-18 17:07:28,518 DEBUG 36
2024-05-18 17:07:28,518 DEBUG zxdg_importer_v2
2024-05-18 17:07:28,518 DEBUG 1
2024-05-18 17:07:28,518 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7fab474b63c0>
2024-05-18 17:07:28,518 DEBUG 37
2024-05-18 17:07:28,518 DEBUG xdg_activation_v1
2024-05-18 17:07:28,518 DEBUG 1
2024-05-18 17:07:28,522 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7fab474b63c0>
2024-05-18 17:07:28,522 DEBUG 38
2024-05-18 17:07:28,522 DEBUG zwp_virtual_keyboard_manager_v1
2024-05-18 17:07:28,522 DEBUG 1
2024-05-18 17:07:28,522 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7fab474b63c0>
2024-05-18 17:07:28,522 DEBUG 39
2024-05-18 17:07:28,522 DEBUG zwlr_virtual_pointer_manager_v1
2024-05-18 17:07:28,522 DEBUG 2
2024-05-18 17:07:28,522 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7fab474b63c0>
2024-05-18 17:07:28,522 DEBUG 40
2024-05-18 17:07:28,522 DEBUG zwlr_input_inhibit_manager_v1
2024-05-18 17:07:28,522 DEBUG 1
2024-05-18 17:07:28,523 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7fab474b63c0>
2024-05-18 17:07:28,523 DEBUG 41
2024-05-18 17:07:28,523 DEBUG zwp_keyboard_shortcuts_inhibit_manager_v1
2024-05-18 17:07:28,523 DEBUG 1
2024-05-18 17:07:28,523 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7fab474b63c0>
2024-05-18 17:07:28,523 DEBUG 42
2024-05-18 17:07:28,523 DEBUG wl_seat
2024-05-18 17:07:28,523 DEBUG 8
2024-05-18 17:07:28,524 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7fab474b63c0>
2024-05-18 17:07:28,530 DEBUG 43
2024-05-18 17:07:28,530 DEBUG zwp_pointer_gestures_v1
2024-05-18 17:07:28,530 DEBUG 3
2024-05-18 17:07:28,530 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7fab474b63c0>
2024-05-18 17:07:28,530 DEBUG 44
2024-05-18 17:07:28,530 DEBUG wl_output
2024-05-18 17:07:28,530 DEBUG 4
2024-05-18 17:07:28,568 DEBUG Wayland will try to load keymap
2024-05-18 17:07:28,690 DEBUG Wayland loaded keymap succesfully
2024-05-18 17:07:28,690 DEBUG {'Num_Lock': KEY_NUMLOCK:69, '0': KEY_0:11, '1': KEY_1:2, '2': KEY_2:3, '3': KEY_3:4, '4': KEY_4:5, '5': KEY_5:6, '6': KEY_6:7, '7': KEY_7:8, '8': KEY_8:9, '9': KEY_9:10, 'a': KEY_A:30, 'b': KEY_B:48, 'c': KEY_C:46, 'd': KEY_D:32, 'e': KEY_E:18, 'f': KEY_F:33, 'Shift_L': KEY_LEFTSHIFT:42, 'Control_L': KEY_LEFTCTRL:29, 'u': KEY_U:22, 'space': KEY_SPACE:57, 'slash': KEY_SLASH:53, 'BackSpace': KEY_BACKSPACE:14, 'asterisk': [KEY_LEFTSHIFT:42, KEY_8:9], 'minus': KEY_MINUS:12, 'percent': [KEY_LEFTSHIFT:42, KEY_5:6], 'period': KEY_DOT:52, 'Return': KEY_ENTER:28, 'plus': [KEY_LEFTSHIFT:42, KEY_EQUAL:13], 'equal': KEY_EQUAL:13}
2024-05-18 17:07:29,205 DEBUG Writting to config file: "<_io.TextIOWrapper name='./numberpad_dev' mode='w' encoding='UTF-8'>"
from asus-numberpad-driver.
irvng-wav
commented on August 15, 2024
Hey @ldrahnik! I saw your ping earlier. Thank you for the reminder, just had time to test the new branch. Here's the log:
[irvng@arch-zenbook ~]$ LOG=DEBUG /usr/share/asus-numberpad-driver/.env/bin/python3 /usr/share/asus-numberpad-driver/numberpad.py up5401ea
2024-05-23 20:40:58,791 INFO Detecting keyboard from string: "N: Name="AT Translated Set 2 keyboard""
2024-05-23 20:40:58,791 INFO Set keyboard 4 from H: Handlers=sysrq kbd leds event4
2024-05-23 20:40:58,818 INFO Detecting touchpad from string: "N: Name="ASUE140D:00 04F3:31B9 Touchpad""
2024-05-23 20:40:58,818 INFO Set touchpad device id 15 from S: Sysfs=/devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-15/i2c-ASUE140D:00/0018:04F3:31B9.0001/input/input13
2024-05-23 20:40:58,818 INFO Set touchpad id 10 from H: Handlers=event10 mouse1
2024-05-23 20:40:58,819 INFO Touchpad min-max: x 0-3880, y 0-2299
2024-05-23 20:40:58,819 INFO Numpad min-max: x 200-3680, y 200-2219
2024-05-23 20:40:58,836 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7bddb5307320>
2024-05-23 20:40:58,836 DEBUG 1
2024-05-23 20:40:58,841 DEBUG wl_compositor
2024-05-23 20:40:58,841 DEBUG 6
2024-05-23 20:40:58,842 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7bddb5307320>
2024-05-23 20:40:58,842 DEBUG 2
2024-05-23 20:40:58,842 DEBUG wl_drm
2024-05-23 20:40:58,842 DEBUG 2
2024-05-23 20:40:58,842 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7bddb5307320>
2024-05-23 20:40:58,842 DEBUG 3
2024-05-23 20:40:58,842 DEBUG wl_shm
2024-05-23 20:40:58,842 DEBUG 1
2024-05-23 20:40:58,842 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7bddb5307320>
2024-05-23 20:40:58,842 DEBUG 4
2024-05-23 20:40:58,842 DEBUG wl_output
2024-05-23 20:40:58,842 DEBUG 4
2024-05-23 20:40:58,847 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7bddb5307320>
2024-05-23 20:40:58,852 DEBUG 5
2024-05-23 20:40:58,852 DEBUG zxdg_output_manager_v1
2024-05-23 20:40:58,852 DEBUG 3
2024-05-23 20:40:58,852 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7bddb5307320>
2024-05-23 20:40:58,852 DEBUG 6
2024-05-23 20:40:58,852 DEBUG wl_data_device_manager
2024-05-23 20:40:58,852 DEBUG 3
2024-05-23 20:40:58,852 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7bddb5307320>
2024-05-23 20:40:58,853 DEBUG 7
2024-05-23 20:40:58,853 DEBUG zwp_primary_selection_device_manager_v1
2024-05-23 20:40:58,853 DEBUG 1
2024-05-23 20:40:58,853 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7bddb5307320>
2024-05-23 20:40:58,853 DEBUG 8
2024-05-23 20:40:58,853 DEBUG wl_subcompositor
2024-05-23 20:40:58,853 DEBUG 1
2024-05-23 20:40:58,853 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7bddb5307320>
2024-05-23 20:40:58,853 DEBUG 9
2024-05-23 20:40:58,853 DEBUG xdg_wm_base
2024-05-23 20:40:58,853 DEBUG 6
2024-05-23 20:40:58,853 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7bddb5307320>
2024-05-23 20:40:58,853 DEBUG 10
2024-05-23 20:40:58,853 DEBUG gtk_shell1
2024-05-23 20:40:58,853 DEBUG 5
2024-05-23 20:40:58,853 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7bddb5307320>
2024-05-23 20:40:58,853 DEBUG 11
2024-05-23 20:40:58,853 DEBUG wp_viewporter
2024-05-23 20:40:58,853 DEBUG 1
2024-05-23 20:40:58,853 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7bddb5307320>
2024-05-23 20:40:58,853 DEBUG 12
2024-05-23 20:40:58,853 DEBUG wp_fractional_scale_manager_v1
2024-05-23 20:40:58,853 DEBUG 1
2024-05-23 20:40:58,853 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7bddb5307320>
2024-05-23 20:40:58,853 DEBUG 13
2024-05-23 20:40:58,853 DEBUG zwp_pointer_gestures_v1
2024-05-23 20:40:58,853 DEBUG 3
2024-05-23 20:40:58,853 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7bddb5307320>
2024-05-23 20:40:58,853 DEBUG 14
2024-05-23 20:40:58,853 DEBUG zwp_tablet_manager_v2
2024-05-23 20:40:58,853 DEBUG 1
2024-05-23 20:40:58,853 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7bddb5307320>
2024-05-23 20:40:58,853 DEBUG 15
2024-05-23 20:40:58,853 DEBUG wl_seat
2024-05-23 20:40:58,853 DEBUG 8
2024-05-23 20:40:58,864 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7bddb5307320>
2024-05-23 20:40:58,869 DEBUG 16
2024-05-23 20:40:58,869 DEBUG zwp_relative_pointer_manager_v1
2024-05-23 20:40:58,869 DEBUG 1
2024-05-23 20:40:58,869 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7bddb5307320>
2024-05-23 20:40:58,869 DEBUG 17
2024-05-23 20:40:58,869 DEBUG zwp_pointer_constraints_v1
2024-05-23 20:40:58,869 DEBUG 1
2024-05-23 20:40:58,869 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7bddb5307320>
2024-05-23 20:40:58,869 DEBUG 18
2024-05-23 20:40:58,869 DEBUG zxdg_exporter_v2
2024-05-23 20:40:58,869 DEBUG 1
2024-05-23 20:40:58,869 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7bddb5307320>
2024-05-23 20:40:58,869 DEBUG 19
2024-05-23 20:40:58,869 DEBUG zxdg_importer_v2
2024-05-23 20:40:58,869 DEBUG 1
2024-05-23 20:40:58,875 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7bddb5307320>
2024-05-23 20:40:58,880 DEBUG 20
2024-05-23 20:40:58,885 DEBUG zxdg_exporter_v1
2024-05-23 20:40:58,891 DEBUG 1
2024-05-23 20:40:58,891 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7bddb5307320>
2024-05-23 20:40:58,891 DEBUG 21
2024-05-23 20:40:58,891 DEBUG zxdg_importer_v1
2024-05-23 20:40:58,891 DEBUG 1
2024-05-23 20:40:58,891 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7bddb5307320>
2024-05-23 20:40:58,891 DEBUG 22
2024-05-23 20:40:58,891 DEBUG zwp_linux_dmabuf_v1
2024-05-23 20:40:58,891 DEBUG 5
2024-05-23 20:40:58,891 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7bddb5307320>
2024-05-23 20:40:58,891 DEBUG 23
2024-05-23 20:40:58,891 DEBUG wp_single_pixel_buffer_manager_v1
2024-05-23 20:40:58,891 DEBUG 1
2024-05-23 20:40:58,891 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7bddb5307320>
2024-05-23 20:40:58,897 DEBUG 24
2024-05-23 20:40:58,897 DEBUG zwp_keyboard_shortcuts_inhibit_manager_v1
2024-05-23 20:40:58,897 DEBUG 1
2024-05-23 20:40:58,897 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7bddb5307320>
2024-05-23 20:40:58,897 DEBUG 25
2024-05-23 20:40:58,897 DEBUG zwp_text_input_manager_v3
2024-05-23 20:40:58,897 DEBUG 1
2024-05-23 20:40:58,897 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7bddb5307320>
2024-05-23 20:40:58,897 DEBUG 26
2024-05-23 20:40:58,897 DEBUG wp_presentation
2024-05-23 20:40:58,897 DEBUG 1
2024-05-23 20:40:58,897 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7bddb5307320>
2024-05-23 20:40:58,897 DEBUG 27
2024-05-23 20:40:58,897 DEBUG xdg_activation_v1
2024-05-23 20:40:58,897 DEBUG 1
2024-05-23 20:40:58,897 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7bddb5307320>
2024-05-23 20:40:58,897 DEBUG 28
2024-05-23 20:40:58,902 DEBUG zwp_idle_inhibit_manager_v1
2024-05-23 20:40:58,908 DEBUG 1
2024-05-23 20:40:58,908 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7bddb5307320>
2024-05-23 20:40:58,908 DEBUG 29
2024-05-23 20:40:58,908 DEBUG wp_linux_drm_syncobj_manager_v1
2024-05-23 20:40:58,908 DEBUG 1
2024-05-23 20:40:58,943 DEBUG Wayland will try to load keymap
2024-05-23 20:41:04,141 DEBUG Wayland loaded keymap succesfully
2024-05-23 20:41:04,141 DEBUG {'Num_Lock': KEY_NUMLOCK:69, '0': KEY_0:11, '1': KEY_1:2, '2': KEY_2:3, '3': KEY_3:4, '4': KEY_4:5, '5': KEY_5:6, '6': KEY_6:7, '7': KEY_7:8, '8': KEY_8:9, '9': KEY_9:10, 'a': KEY_A:30, 'b': KEY_B:48, 'c': KEY_C:46, 'd': KEY_D:32, 'e': KEY_E:18, 'f': KEY_F:33, 'Shift_L': KEY_LEFTSHIFT:42, 'Control_L': KEY_LEFTCTRL:29, 'u': KEY_U:22, 'space': KEY_SPACE:57, 'slash': [KEY_LEFTSHIFT:42, KEY_7:8], 'BackSpace': KEY_BACKSPACE:14, 'asterisk': [KEY_LEFTSHIFT:42, KEY_RIGHTBRACE:27], 'minus': KEY_SLASH:53, 'percent': [KEY_LEFTSHIFT:42, KEY_5:6], 'period': KEY_DOT:52, 'Return': KEY_ENTER:28, 'plus': KEY_RIGHTBRACE:27, 'equal': [KEY_LEFTSHIFT:42, KEY_0:11]}
2024-05-23 20:41:04,644 INFO Setting up for config file key: "brightness" with value: "0x48"
2024-05-23 20:41:04,644 DEBUG Writting to config file: "<_io.TextIOWrapper name='./numberpad_dev' mode='w' encoding='UTF-8'>"
2024-05-23 20:41:04,752 ERROR Listening touchpad events unexpectedly failed
Traceback (most recent call last):
File "/usr/share/asus-numberpad-driver/numberpad.py", line 2431, in <module>
listen_touchpad_events()
File "/usr/share/asus-numberpad-driver/numberpad.py", line 1953, in listen_touchpad_events
for e in d_t.events():
File "/usr/share/asus-numberpad-driver/.env/lib/python3.12/site-packages/libevdev/device.py", line 541, in events
raise EventsDroppedException()
libevdev.device.EventsDroppedException
2024-05-23 20:41:04,754 INFO Clean up started
[2024-05-23 20:41:04,828 pyinotify ERROR] Cannot delete unknown watch descriptor '/home/irvng'
2024-05-23 20:41:04,828 ERROR Cannot delete unknown watch descriptor '/home/irvng'
2024-05-23 20:41:04,828 INFO Clean up finished
2024-05-23 20:41:04,828 INFO Exiting
[irvng@arch-zenbook ~]$
The driver is working correctly. Although at first I thought it wasn't working but it might have been me not pressing the numpad on/off button for the needed ammount of time. Let me reboot my laptop and try again.
from asus-numberpad-driver.
irvng-wav
commented on August 15, 2024
Ok just restarted my computer and the numpad is working right from the start. That's great! Here's the error.log from this testing session:
error.log
So I stopped the systemctl service, then manually started it wth LOG=DEBUG. Here are the logs:
[irvng@arch-zenbook ~]$ systemctl stop --user [email protected]
[irvng@arch-zenbook ~]$ LOG=DEBUG /usr/share/asus-numberpad-driver/.env/bin/python3 /usr/share/asus-numberpad-driver/numberpad.py up5401ea
2024-05-23 20:57:51,043 INFO Detecting keyboard from string: "N: Name="AT Translated Set 2 keyboard""
2024-05-23 20:57:51,043 INFO Set keyboard 4 from H: Handlers=sysrq kbd leds event4
2024-05-23 20:57:51,066 INFO Detecting touchpad from string: "N: Name="ASUE140D:00 04F3:31B9 Touchpad""
2024-05-23 20:57:51,066 INFO Set touchpad device id 15 from S: Sysfs=/devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-15/i2c-ASUE140D:00/0018:04F3:31B9.0001/input/input13
2024-05-23 20:57:51,066 INFO Set touchpad id 10 from H: Handlers=event10 mouse1
2024-05-23 20:57:51,067 INFO Touchpad min-max: x 0-3880, y 0-2299
2024-05-23 20:57:51,067 INFO Numpad min-max: x 200-3680, y 200-2219
2024-05-23 20:57:51,079 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7316e23f6ea0>
2024-05-23 20:57:51,079 DEBUG 1
2024-05-23 20:57:51,079 DEBUG wl_compositor
2024-05-23 20:57:51,079 DEBUG 6
2024-05-23 20:57:51,079 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7316e23f6ea0>
2024-05-23 20:57:51,079 DEBUG 2
2024-05-23 20:57:51,079 DEBUG wl_drm
2024-05-23 20:57:51,079 DEBUG 2
2024-05-23 20:57:51,079 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7316e23f6ea0>
2024-05-23 20:57:51,079 DEBUG 3
2024-05-23 20:57:51,079 DEBUG wl_shm
2024-05-23 20:57:51,079 DEBUG 1
2024-05-23 20:57:51,079 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7316e23f6ea0>
2024-05-23 20:57:51,079 DEBUG 4
2024-05-23 20:57:51,079 DEBUG wl_output
2024-05-23 20:57:51,079 DEBUG 4
2024-05-23 20:57:51,079 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7316e23f6ea0>
2024-05-23 20:57:51,080 DEBUG 5
2024-05-23 20:57:51,085 DEBUG zxdg_output_manager_v1
2024-05-23 20:57:51,090 DEBUG 3
2024-05-23 20:57:51,090 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7316e23f6ea0>
2024-05-23 20:57:51,095 DEBUG 6
2024-05-23 20:57:51,095 DEBUG wl_data_device_manager
2024-05-23 20:57:51,095 DEBUG 3
2024-05-23 20:57:51,096 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7316e23f6ea0>
2024-05-23 20:57:51,096 DEBUG 7
2024-05-23 20:57:51,096 DEBUG zwp_primary_selection_device_manager_v1
2024-05-23 20:57:51,096 DEBUG 1
2024-05-23 20:57:51,096 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7316e23f6ea0>
2024-05-23 20:57:51,096 DEBUG 8
2024-05-23 20:57:51,096 DEBUG wl_subcompositor
2024-05-23 20:57:51,096 DEBUG 1
2024-05-23 20:57:51,096 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7316e23f6ea0>
2024-05-23 20:57:51,096 DEBUG 9
2024-05-23 20:57:51,096 DEBUG xdg_wm_base
2024-05-23 20:57:51,096 DEBUG 6
2024-05-23 20:57:51,101 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7316e23f6ea0>
2024-05-23 20:57:51,101 DEBUG 10
2024-05-23 20:57:51,101 DEBUG gtk_shell1
2024-05-23 20:57:51,101 DEBUG 5
2024-05-23 20:57:51,101 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7316e23f6ea0>
2024-05-23 20:57:51,101 DEBUG 11
2024-05-23 20:57:51,106 DEBUG wp_viewporter
2024-05-23 20:57:51,106 DEBUG 1
2024-05-23 20:57:51,106 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7316e23f6ea0>
2024-05-23 20:57:51,106 DEBUG 12
2024-05-23 20:57:51,107 DEBUG wp_fractional_scale_manager_v1
2024-05-23 20:57:51,107 DEBUG 1
2024-05-23 20:57:51,107 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7316e23f6ea0>
2024-05-23 20:57:51,107 DEBUG 13
2024-05-23 20:57:51,107 DEBUG zwp_pointer_gestures_v1
2024-05-23 20:57:51,107 DEBUG 3
2024-05-23 20:57:51,112 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7316e23f6ea0>
2024-05-23 20:57:51,117 DEBUG 14
2024-05-23 20:57:51,122 DEBUG zwp_tablet_manager_v2
2024-05-23 20:57:51,128 DEBUG 1
2024-05-23 20:57:51,138 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7316e23f6ea0>
2024-05-23 20:57:51,143 DEBUG 15
2024-05-23 20:57:51,149 DEBUG wl_seat
2024-05-23 20:57:51,154 DEBUG 8
2024-05-23 20:57:51,170 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7316e23f6ea0>
2024-05-23 20:57:51,175 DEBUG 16
2024-05-23 20:57:51,180 DEBUG zwp_relative_pointer_manager_v1
2024-05-23 20:57:51,185 DEBUG 1
2024-05-23 20:57:51,196 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7316e23f6ea0>
2024-05-23 20:57:51,201 DEBUG 17
2024-05-23 20:57:51,206 DEBUG zwp_pointer_constraints_v1
2024-05-23 20:57:51,211 DEBUG 1
2024-05-23 20:57:51,222 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7316e23f6ea0>
2024-05-23 20:57:51,227 DEBUG 18
2024-05-23 20:57:51,232 DEBUG zxdg_exporter_v2
2024-05-23 20:57:51,238 DEBUG 1
2024-05-23 20:57:51,248 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7316e23f6ea0>
2024-05-23 20:57:51,253 DEBUG 19
2024-05-23 20:57:51,259 DEBUG zxdg_importer_v2
2024-05-23 20:57:51,264 DEBUG 1
2024-05-23 20:57:51,274 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7316e23f6ea0>
2024-05-23 20:57:51,279 DEBUG 20
2024-05-23 20:57:51,285 DEBUG zxdg_exporter_v1
2024-05-23 20:57:51,290 DEBUG 1
2024-05-23 20:57:51,295 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7316e23f6ea0>
2024-05-23 20:57:51,300 DEBUG 21
2024-05-23 20:57:51,306 DEBUG zxdg_importer_v1
2024-05-23 20:57:51,311 DEBUG 1
2024-05-23 20:57:51,316 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7316e23f6ea0>
2024-05-23 20:57:51,321 DEBUG 22
2024-05-23 20:57:51,327 DEBUG zwp_linux_dmabuf_v1
2024-05-23 20:57:51,332 DEBUG 5
2024-05-23 20:57:51,342 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7316e23f6ea0>
2024-05-23 20:57:51,348 DEBUG 23
2024-05-23 20:57:51,353 DEBUG wp_single_pixel_buffer_manager_v1
2024-05-23 20:57:51,358 DEBUG 1
2024-05-23 20:57:51,368 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7316e23f6ea0>
2024-05-23 20:57:51,374 DEBUG 24
2024-05-23 20:57:51,379 DEBUG zwp_keyboard_shortcuts_inhibit_manager_v1
2024-05-23 20:57:51,384 DEBUG 1
2024-05-23 20:57:51,389 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7316e23f6ea0>
2024-05-23 20:57:51,395 DEBUG 25
2024-05-23 20:57:51,400 DEBUG zwp_text_input_manager_v3
2024-05-23 20:57:51,405 DEBUG 1
2024-05-23 20:57:51,410 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7316e23f6ea0>
2024-05-23 20:57:51,416 DEBUG 26
2024-05-23 20:57:51,421 DEBUG wp_presentation
2024-05-23 20:57:51,426 DEBUG 1
2024-05-23 20:57:51,437 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7316e23f6ea0>
2024-05-23 20:57:51,442 DEBUG 27
2024-05-23 20:57:51,447 DEBUG xdg_activation_v1
2024-05-23 20:57:51,452 DEBUG 1
2024-05-23 20:57:51,463 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7316e23f6ea0>
2024-05-23 20:57:51,468 DEBUG 28
2024-05-23 20:57:51,473 DEBUG zwp_idle_inhibit_manager_v1
2024-05-23 20:57:51,478 DEBUG 1
2024-05-23 20:57:51,489 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7316e23f6ea0>
2024-05-23 20:57:51,494 DEBUG 29
2024-05-23 20:57:51,499 DEBUG wp_linux_drm_syncobj_manager_v1
2024-05-23 20:57:51,504 DEBUG 1
2024-05-23 20:57:51,533 DEBUG Wayland will try to load keymap
2024-05-23 20:57:57,466 DEBUG Wayland loaded keymap succesfully
2024-05-23 20:57:57,466 DEBUG {'Num_Lock': KEY_NUMLOCK:69, '0': KEY_0:11, '1': KEY_1:2, '2': KEY_2:3, '3': KEY_3:4, '4': KEY_4:5, '5': KEY_5:6, '6': KEY_6:7, '7': KEY_7:8, '8': KEY_8:9, '9': KEY_9:10, 'a': KEY_A:30, 'b': KEY_B:48, 'c': KEY_C:46, 'd': KEY_D:32, 'e': KEY_E:18, 'f': KEY_F:33, 'Shift_L': KEY_LEFTSHIFT:42, 'Control_L': KEY_LEFTCTRL:29, 'u': KEY_U:22, 'space': KEY_SPACE:57, 'slash': [KEY_LEFTSHIFT:42, KEY_7:8], 'BackSpace': KEY_BACKSPACE:14, 'asterisk': [KEY_LEFTSHIFT:42, KEY_RIGHTBRACE:27], 'minus': KEY_SLASH:53, 'percent': [KEY_LEFTSHIFT:42, KEY_5:6], 'period': KEY_DOT:52, 'Return': KEY_ENTER:28, 'plus': KEY_RIGHTBRACE:27, 'equal': [KEY_LEFTSHIFT:42, KEY_0:11]}
2024-05-23 20:57:57,971 DEBUG Writting to config file: "<_io.TextIOWrapper name='./numberpad_dev' mode='w' encoding='UTF-8'>"
2024-05-23 20:57:58,083 DEBUG Started new slot
2024-05-23 20:57:58,085 DEBUG finger down at x 3804 y 14
2024-05-23 20:57:58,085 INFO Touched top_right_icon area (numlock) in time: 1716519478.0852616
2024-05-23 20:57:59,089 INFO The numpad numlock was pressed longer than the activation time and will be activated: 1.003612756729126
2024-05-23 20:57:59,089 INFO Activation time: 1.0
2024-05-23 20:57:59,123 INFO System numlock activated
2024-05-23 20:57:59,123 INFO Numpad activated
2024-05-23 20:57:59,123 DEBUG ['gsettings', 'set', 'org.gnome.desktop.peripherals.touchpad', 'tap-to-click', 'false']
2024-05-23 20:57:59,140 DEBUG ['xinput', 'set-prop', 'ASUE140D:00 04F3:31B9 Touchpad', 'libinput Tapping Enabled', '0']
WARNING: running xinput against an Xwayland server. See the xinput man page for details.
unable to find device ASUE140D:00 04F3:31B9 Touchpad
2024-05-23 20:57:59,146 INFO Setting up for config file key: "enabled" with value: "True"
2024-05-23 20:57:59,147 DEBUG Writting to config file: "<_io.TextIOWrapper name='./numberpad_dev' mode='w' encoding='UTF-8'>"
2024-05-23 20:57:59,147 INFO check_config_values_changes: detected internal change of config file -> do nothing -> would be deadlock
<Event dir=False mask=0x8 maskname=IN_CLOSE_WRITE name=numberpad_dev path=/home/irvng pathname=/home/irvng/numberpad_dev wd=1 >
2024-05-23 20:57:59,753 DEBUG Ended existing slot
2024-05-23 20:57:59,754 DEBUG finger down at x 3787 y 34
2024-05-23 20:57:59,754 INFO Un-touched top_right_icon area (representing numlock key) in time: 1716519479.754318
2024-05-23 20:58:02,539 DEBUG Started new slot
2024-05-23 20:58:02,540 DEBUG finger down at x 3834 y 23
2024-05-23 20:58:02,540 INFO Touched top_right_icon area (numlock) in time: 1716519482.5406203
2024-05-23 20:58:03,545 INFO The numpad numlock was pressed longer than the activation time and will be activated: 1.0052056312561035
2024-05-23 20:58:03,546 INFO Activation time: 1.0
2024-05-23 20:58:03,586 INFO System numlock deactivated
2024-05-23 20:58:03,586 INFO Numpad deactivated
2024-05-23 20:58:03,587 DEBUG ['gsettings', 'set', 'org.gnome.desktop.peripherals.touchpad', 'tap-to-click', 'true']
2024-05-23 20:58:03,604 DEBUG ['xinput', 'set-prop', 'ASUE140D:00 04F3:31B9 Touchpad', 'libinput Tapping Enabled', '1']
WARNING: running xinput against an Xwayland server. See the xinput man page for details.
unable to find device ASUE140D:00 04F3:31B9 Touchpad
2024-05-23 20:58:03,610 INFO Setting up for config file key: "enabled" with value: "False"
2024-05-23 20:58:03,610 DEBUG Writting to config file: "<_io.TextIOWrapper name='./numberpad_dev' mode='w' encoding='UTF-8'>"
2024-05-23 20:58:03,610 INFO check_config_values_changes: detected internal change of config file -> do nothing -> would be deadlock
<Event dir=False mask=0x8 maskname=IN_CLOSE_WRITE name=numberpad_dev path=/home/irvng pathname=/home/irvng/numberpad_dev wd=1 >
2024-05-23 20:58:04,217 DEBUG Ended existing slot
2024-05-23 20:58:04,218 DEBUG finger down at x 3804 y 61
2024-05-23 20:58:04,218 INFO Un-touched top_right_icon area (representing numlock key) in time: 1716519484.2182581
2024-05-23 20:58:05,874 DEBUG Started new slot
2024-05-23 20:58:05,874 DEBUG finger down at x 1794 y 1821
2024-05-23 20:58:06,064 DEBUG Ended existing slot
2024-05-23 20:58:06,066 DEBUG finger down at x 1645 y 1245
2024-05-23 20:58:06,066 DEBUG key unpress was already handled because slot is empty
2024-05-23 20:58:06,216 DEBUG Started new slot
2024-05-23 20:58:06,217 DEBUG finger down at x 1667 y 1611
2024-05-23 20:58:07,282 DEBUG Ended existing slot
2024-05-23 20:58:07,284 DEBUG finger down at x 1556 y 1819
2024-05-23 20:58:07,284 DEBUG key unpress was already handled because slot is empty
2024-05-23 20:58:07,476 DEBUG Started new slot
2024-05-23 20:58:07,478 DEBUG finger down at x 1689 y 1830
2024-05-23 20:58:07,898 DEBUG Ended existing slot
2024-05-23 20:58:07,900 DEBUG finger down at x 1728 y 1707
2024-05-23 20:58:07,900 DEBUG key unpress was already handled because slot is empty
^C2024-05-23 20:58:08,863 ERROR Listening touchpad events unexpectedly failed
Traceback (most recent call last):
File "/usr/share/asus-numberpad-driver/numberpad.py", line 2431, in <module>
listen_touchpad_events()
File "/usr/share/asus-numberpad-driver/numberpad.py", line 1953, in listen_touchpad_events
for e in d_t.events():
File "/usr/share/asus-numberpad-driver/.env/lib/python3.12/site-packages/libevdev/device.py", line 542, in events
ev = self._libevdev.next_event(flags)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/share/asus-numberpad-driver/.env/lib/python3.12/site-packages/libevdev/_clib.py", line 889, in next_event
rc = self._next_event(self._ctx, flags, ctypes.byref(ev))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
KeyboardInterrupt
2024-05-23 20:58:08,876 INFO Clean up started
[2024-05-23 20:58:08,896 pyinotify ERROR] Cannot delete unknown watch descriptor '/home/irvng'
2024-05-23 20:58:08,896 ERROR Cannot delete unknown watch descriptor '/home/irvng'
2024-05-23 20:58:08,896 INFO Clean up finished
2024-05-23 20:58:08,897 INFO Exiting
from asus-numberpad-driver.
ldrahnik
commented on August 15, 2024
@irvng-wav May I close this issue as completed? or any problem persists?
from asus-numberpad-driver.
ldrahnik
commented on August 15, 2024
@kamack38 Could you please confirm it works too? I tried installing driver on garuda in the virtual box yesterday and it works fine.
from asus-numberpad-driver.
irvng-wav
commented on August 15, 2024
For some reason the numpad service isn't working correctly when I boot up my system. I rebooted twice and had to start the service manually. Here is the log:
[irvng@arch-zenbook ~]$ LOG=DEBUG /usr/share/asus-numberpad-driver/.env/bin/python3 /usr/share/asus-numberpad-driver/numberpad.py up5401ea
2024-05-26 01:06:02,436 INFO Detecting keyboard from string: "N: Name="AT Translated Set 2 keyboard""
2024-05-26 01:06:02,436 INFO Set keyboard 4 from H: Handlers=sysrq kbd leds event4
2024-05-26 01:06:02,462 INFO Detecting touchpad from string: "N: Name="ASUE140D:00 04F3:31B9 Touchpad""
2024-05-26 01:06:02,462 INFO Set touchpad device id 15 from S: Sysfs=/devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-15/i2c-ASUE140D:00/0018:04F3:31B9.0001/input/input13
2024-05-26 01:06:02,462 INFO Set touchpad id 10 from H: Handlers=event10 mouse1
2024-05-26 01:06:02,462 INFO Touchpad min-max: x 0-3880, y 0-2299
2024-05-26 01:06:02,462 INFO Numpad min-max: x 200-3680, y 200-2219
2024-05-26 01:06:02,474 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7a6b305faba0>
2024-05-26 01:06:02,479 DEBUG 1
2024-05-26 01:06:02,484 DEBUG wl_compositor
2024-05-26 01:06:02,490 DEBUG 6
2024-05-26 01:06:02,490 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7a6b305faba0>
2024-05-26 01:06:02,490 DEBUG 2
2024-05-26 01:06:02,490 DEBUG wl_drm
2024-05-26 01:06:02,495 DEBUG 2
2024-05-26 01:06:02,500 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7a6b305faba0>
2024-05-26 01:06:02,505 DEBUG 3
2024-05-26 01:06:02,511 DEBUG wl_shm
2024-05-26 01:06:02,511 DEBUG 1
2024-05-26 01:06:02,511 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7a6b305faba0>
2024-05-26 01:06:02,511 DEBUG 4
2024-05-26 01:06:02,511 DEBUG wl_output
2024-05-26 01:06:02,511 DEBUG 4
2024-05-26 01:06:02,511 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7a6b305faba0>
2024-05-26 01:06:02,511 DEBUG 5
2024-05-26 01:06:02,511 DEBUG zxdg_output_manager_v1
2024-05-26 01:06:02,511 DEBUG 3
2024-05-26 01:06:02,516 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7a6b305faba0>
2024-05-26 01:06:02,516 DEBUG 6
2024-05-26 01:06:02,516 DEBUG wl_data_device_manager
2024-05-26 01:06:02,516 DEBUG 3
2024-05-26 01:06:02,516 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7a6b305faba0>
2024-05-26 01:06:02,517 DEBUG 7
2024-05-26 01:06:02,522 DEBUG zwp_primary_selection_device_manager_v1
2024-05-26 01:06:02,522 DEBUG 1
2024-05-26 01:06:02,522 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7a6b305faba0>
2024-05-26 01:06:02,522 DEBUG 8
2024-05-26 01:06:02,522 DEBUG wl_subcompositor
2024-05-26 01:06:02,522 DEBUG 1
2024-05-26 01:06:02,522 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7a6b305faba0>
2024-05-26 01:06:02,522 DEBUG 9
2024-05-26 01:06:02,522 DEBUG xdg_wm_base
2024-05-26 01:06:02,522 DEBUG 6
2024-05-26 01:06:02,522 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7a6b305faba0>
2024-05-26 01:06:02,522 DEBUG 10
2024-05-26 01:06:02,522 DEBUG gtk_shell1
2024-05-26 01:06:02,522 DEBUG 5
2024-05-26 01:06:02,522 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7a6b305faba0>
2024-05-26 01:06:02,522 DEBUG 11
2024-05-26 01:06:02,522 DEBUG wp_viewporter
2024-05-26 01:06:02,522 DEBUG 1
2024-05-26 01:06:02,522 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7a6b305faba0>
2024-05-26 01:06:02,522 DEBUG 12
2024-05-26 01:06:02,522 DEBUG wp_fractional_scale_manager_v1
2024-05-26 01:06:02,522 DEBUG 1
2024-05-26 01:06:02,522 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7a6b305faba0>
2024-05-26 01:06:02,522 DEBUG 13
2024-05-26 01:06:02,522 DEBUG zwp_pointer_gestures_v1
2024-05-26 01:06:02,522 DEBUG 3
2024-05-26 01:06:02,522 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7a6b305faba0>
2024-05-26 01:06:02,522 DEBUG 14
2024-05-26 01:06:02,522 DEBUG zwp_tablet_manager_v2
2024-05-26 01:06:02,522 DEBUG 1
2024-05-26 01:06:02,522 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7a6b305faba0>
2024-05-26 01:06:02,522 DEBUG 15
2024-05-26 01:06:02,523 DEBUG wl_seat
2024-05-26 01:06:02,523 DEBUG 8
2024-05-26 01:06:02,523 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7a6b305faba0>
2024-05-26 01:06:02,523 DEBUG 16
2024-05-26 01:06:02,523 DEBUG zwp_relative_pointer_manager_v1
2024-05-26 01:06:02,523 DEBUG 1
2024-05-26 01:06:02,523 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7a6b305faba0>
2024-05-26 01:06:02,523 DEBUG 17
2024-05-26 01:06:02,523 DEBUG zwp_pointer_constraints_v1
2024-05-26 01:06:02,523 DEBUG 1
2024-05-26 01:06:02,523 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7a6b305faba0>
2024-05-26 01:06:02,523 DEBUG 18
2024-05-26 01:06:02,523 DEBUG zxdg_exporter_v2
2024-05-26 01:06:02,523 DEBUG 1
2024-05-26 01:06:02,523 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7a6b305faba0>
2024-05-26 01:06:02,523 DEBUG 19
2024-05-26 01:06:02,523 DEBUG zxdg_importer_v2
2024-05-26 01:06:02,523 DEBUG 1
2024-05-26 01:06:02,523 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7a6b305faba0>
2024-05-26 01:06:02,523 DEBUG 20
2024-05-26 01:06:02,523 DEBUG zxdg_exporter_v1
2024-05-26 01:06:02,523 DEBUG 1
2024-05-26 01:06:02,523 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7a6b305faba0>
2024-05-26 01:06:02,523 DEBUG 21
2024-05-26 01:06:02,523 DEBUG zxdg_importer_v1
2024-05-26 01:06:02,523 DEBUG 1
2024-05-26 01:06:02,523 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7a6b305faba0>
2024-05-26 01:06:02,523 DEBUG 22
2024-05-26 01:06:02,523 DEBUG zwp_linux_dmabuf_v1
2024-05-26 01:06:02,523 DEBUG 5
2024-05-26 01:06:02,523 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7a6b305faba0>
2024-05-26 01:06:02,523 DEBUG 23
2024-05-26 01:06:02,523 DEBUG wp_single_pixel_buffer_manager_v1
2024-05-26 01:06:02,523 DEBUG 1
2024-05-26 01:06:02,523 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7a6b305faba0>
2024-05-26 01:06:02,523 DEBUG 24
2024-05-26 01:06:02,523 DEBUG zwp_keyboard_shortcuts_inhibit_manager_v1
2024-05-26 01:06:02,523 DEBUG 1
2024-05-26 01:06:02,523 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7a6b305faba0>
2024-05-26 01:06:02,523 DEBUG 25
2024-05-26 01:06:02,523 DEBUG zwp_text_input_manager_v3
2024-05-26 01:06:02,523 DEBUG 1
2024-05-26 01:06:02,523 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7a6b305faba0>
2024-05-26 01:06:02,523 DEBUG 26
2024-05-26 01:06:02,523 DEBUG wp_presentation
2024-05-26 01:06:02,523 DEBUG 1
2024-05-26 01:06:02,523 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7a6b305faba0>
2024-05-26 01:06:02,523 DEBUG 27
2024-05-26 01:06:02,523 DEBUG xdg_activation_v1
2024-05-26 01:06:02,523 DEBUG 1
2024-05-26 01:06:02,523 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7a6b305faba0>
2024-05-26 01:06:02,523 DEBUG 28
2024-05-26 01:06:02,523 DEBUG zwp_idle_inhibit_manager_v1
2024-05-26 01:06:02,523 DEBUG 1
2024-05-26 01:06:02,524 DEBUG <pywayland.protocol.wayland.wl_registry.WlRegistryProxy object at 0x7a6b305faba0>
2024-05-26 01:06:02,524 DEBUG 29
2024-05-26 01:06:02,524 DEBUG wp_linux_drm_syncobj_manager_v1
2024-05-26 01:06:02,524 DEBUG 1
2024-05-26 01:06:02,553 DEBUG Wayland will try to load keymap
2024-05-26 01:06:09,832 DEBUG Wayland loaded keymap succesfully
2024-05-26 01:06:09,832 DEBUG {'Num_Lock': KEY_NUMLOCK:69, '0': KEY_0:11, '1': KEY_1:2, '2': KEY_2:3, '3': KEY_3:4, '4': KEY_4:5, '5': KEY_5:6, '6': KEY_6:7, '7': KEY_7:8, '8': KEY_8:9, '9': KEY_9:10, 'a': KEY_A:30, 'b': KEY_B:48, 'c': KEY_C:46, 'd': KEY_D:32, 'e': KEY_E:18, 'f': KEY_F:33, 'Shift_L': KEY_LEFTSHIFT:42, 'Control_L': KEY_LEFTCTRL:29, 'u': KEY_U:22, 'space': KEY_SPACE:57, 'slash': [KEY_LEFTSHIFT:42, KEY_7:8], 'BackSpace': KEY_BACKSPACE:14, 'asterisk': [KEY_LEFTSHIFT:42, KEY_RIGHTBRACE:27], 'minus': KEY_SLASH:53, 'percent': [KEY_LEFTSHIFT:42, KEY_5:6], 'period': KEY_DOT:52, 'Return': KEY_ENTER:28, 'plus': KEY_RIGHTBRACE:27, 'equal': [KEY_LEFTSHIFT:42, KEY_0:11]}
2024-05-26 01:06:10,335 INFO Setting up for config file key: "brightness" with value: "0x48"
2024-05-26 01:06:10,336 DEBUG Writting to config file: "<_io.TextIOWrapper name='./numberpad_dev' mode='w' encoding='UTF-8'>"
2024-05-26 01:06:10,447 ERROR Listening touchpad events unexpectedly failed
Traceback (most recent call last):
File "/usr/share/asus-numberpad-driver/numberpad.py", line 2431, in <module>
listen_touchpad_events()
File "/usr/share/asus-numberpad-driver/numberpad.py", line 1953, in listen_touchpad_events
for e in d_t.events():
File "/usr/share/asus-numberpad-driver/.env/lib/python3.12/site-packages/libevdev/device.py", line 541, in events
raise EventsDroppedException()
libevdev.device.EventsDroppedException
2024-05-26 01:06:10,450 INFO Clean up started
2024-05-26 01:06:10,479 DEBUG ['gsettings', 'set', 'org.gnome.desktop.peripherals.touchpad', 'tap-to-click', 'false']
2024-05-26 01:06:10,489 DEBUG ['xinput', 'set-prop', 'ASUE140D:00 04F3:31B9 Touchpad', 'libinput Tapping Enabled', '0']
WARNING: running xinput against an Xwayland server. See the xinput man page for details.
unable to find device ASUE140D:00 04F3:31B9 Touchpad
2024-05-26 01:06:10,495 INFO Setting up for config file key: "enabled" with value: "True"
2024-05-26 01:06:10,496 DEBUG Writting to config file: "<_io.TextIOWrapper name='./numberpad_dev' mode='w' encoding='UTF-8'>"
2024-05-26 01:06:10,496 INFO check_config_values_changes: detected internal change of config file -> do nothing -> would be deadlock
<Event dir=False mask=0x8 maskname=IN_CLOSE_WRITE name=numberpad_dev path=/home/irvng pathname=/home/irvng/numberpad_dev wd=1 >
2024-05-26 01:06:10,596 INFO Numpad activated
2024-05-26 01:06:10,639 INFO System numlock deactivated
2024-05-26 01:06:10,640 INFO Setting up for config file key: "idled" with value: "False"
2024-05-26 01:06:10,640 DEBUG Writting to config file: "<_io.TextIOWrapper name='./numberpad_dev' mode='w' encoding='UTF-8'>"
2024-05-26 01:06:10,641 INFO check_config_values_changes: detected internal change of config file -> do nothing -> would be deadlock
<Event dir=False mask=0x8 maskname=IN_CLOSE_WRITE name=numberpad_dev path=/home/irvng pathname=/home/irvng/numberpad_dev wd=1 >
2024-05-26 01:06:10,741 INFO Cancelled numpad idle
2024-05-26 01:06:10,742 INFO Cancelled idle
2024-05-26 01:06:10,742 DEBUG ['gsettings', 'set', 'org.gnome.desktop.peripherals.touchpad', 'tap-to-click', 'true']
2024-05-26 01:06:10,751 DEBUG ['xinput', 'set-prop', 'ASUE140D:00 04F3:31B9 Touchpad', 'libinput Tapping Enabled', '1']
WARNING: running xinput against an Xwayland server. See the xinput man page for details.
unable to find device ASUE140D:00 04F3:31B9 Touchpad
2024-05-26 01:06:10,756 INFO Setting up for config file key: "enabled" with value: "False"
2024-05-26 01:06:10,756 DEBUG Writting to config file: "<_io.TextIOWrapper name='./numberpad_dev' mode='w' encoding='UTF-8'>"
2024-05-26 01:06:10,757 INFO check_config_values_changes: detected internal change of config file -> do nothing -> would be deadlock
<Event dir=False mask=0x8 maskname=IN_CLOSE_WRITE name=numberpad_dev path=/home/irvng pathname=/home/irvng/numberpad_dev wd=1 >
2024-05-26 01:06:10,857 INFO Numpad deactivated
[2024-05-26 01:06:10,885 pyinotify ERROR] Cannot delete unknown watch descriptor '/home/irvng'
2024-05-26 01:06:10,885 ERROR Cannot delete unknown watch descriptor '/home/irvng'
2024-05-26 01:06:10,886 INFO Clean up finished
2024-05-26 01:06:10,886 INFO Exiting
Edit
Rebooted a third time and also powered off, then powered on the laptop and the numpad isn't automatically started. When I run systemctl status --user [email protected] I get this output:
[irvng@arch-zenbook ~]$ systemctl status --user [email protected]
● [email protected] - Asus NumberPad Driver
Loaded: loaded (/usr/lib/systemd/user/[email protected];
enabled; preset: enabled)
Active: active (running) since Sun 2024-05-26 01:12:36 CST; 8s a
go
Main PID: 14820 (python3)
Tasks: 17 (limit: 18700)
Memory: 30.2M (peak: 31.1M)
CPU: 9.460s
CGroup: /user.slice/user-1000.slice/[email protected]/app.slice/app-asus_nu
mberpad_driver.slice/[email protected]
└─14820 /usr/share/asus-numberpad-driver/.env/bin/pytho
n3 /usr/share/asus-numberpad-driver/numberpad.py up5401ea /usr/share/asus-number
pad-driver/
may 26 01:12:35 arch-zenbook systemd[5034]: [email protected]:
Consumed 6.259s CPU time.
may 26 01:12:35 arch-zenbook systemd[5034]: [email protected]:
Scheduled restart job, restart counter is at 17.
may 26 01:12:36 arch-zenbook systemd[5034]: Started Asus NumberPad Driver.
After some time the numpad started working.
Edit 2
Rebooted again and ran the status check command multiple times while the numpad didn't show any signs of life. Here's the output:
[irvng@arch-zenbook ~]$ systemctl status --user [email protected]
● [email protected] - Asus NumberPad Driver
Loaded: loaded (/usr/lib/systemd/user/[email protected];
enabled; preset: enabled)
Active: active (running) since Sun 2024-05-26 01:25:35 CST; 4s a
go
Main PID: 25340 (python3)
Tasks: 17 (limit: 18700)
Memory: 30.2M (peak: 31.8M)
CPU: 5.931s
CGroup: /user.slice/user-1000.slice/[email protected]/app.slice/app-asus_nu
mberpad_driver.slice/[email protected]
└─25340 /usr/share/asus-numberpad-driver/.env/bin/pytho
n3 /usr/share/asus-numberpad-driver/numberpad.py up5401ea /usr/share/asus-number
pad-driver/
may 26 01:25:35 arch-zenbook systemd[5191]:
[email protected]: Failed with result 'exit-code'.
may 26 01:25:35 arch-zenbook systemd[5191]: [email protected]:
Consumed 8.811s CPU time.
may 26 01:25:35 arch-zenbook systemd[5191]: [email protected]:
Scheduled restart job, restart counter is at 31.
may 26 01:25:35 arch-zenbook systemd[5191]: Started Asus NumberPad Driver.
Then again, the numpad started working after some time and systemctl status now showed this:
[irvng@arch-zenbook ~]$ systemctl status --user [email protected]
● [email protected] - Asus NumberPad Driver
Loaded: loaded (/usr/lib/systemd/user/[email protected];
enabled; preset: enabled)
Active: active (running) since Sun 2024-05-26 01:27:20 CST; 13s ago
Main PID: 35093 (python3)
Tasks: 22 (limit: 18700)
Memory: 30.9M (peak: 33.5M)
CPU: 8.082s
CGroup: /user.slice/user-1000.slice/[email protected]/app.slice/app-asus_numberpad_driver.slice/[email protected]
└─35093 /usr/share/asus-numberpad-driver/.env/bin/python3 /usr/share/asus-numberpad-driver/numberpad.py up5401ea /usr/share/asus-n
umberpad-driver/
may 26 01:27:20 arch-zenbook systemd[5191]: [email protected]: Failed with result 'exit-code'.
may 26 01:27:20 arch-zenbook systemd[5191]: [email protected]: Consumed 8.715s CPU time.
may 26 01:27:20 arch-zenbook systemd[5191]: [email protected]: Scheduled restart job, restart counter is at 43.
may 26 01:27:20 arch-zenbook systemd[5191]: Started Asus NumberPad Driver.
from asus-numberpad-driver.
ldrahnik
commented on August 15, 2024
@irvng-wav Please, download the latest master, add this line Environment="LOG=DEBUG" at the end of file asus_numberpad_driver.wayland.service and install & reboot, and post the clean error log here again.
from asus-numberpad-driver.
irvng-wav
commented on August 15, 2024
@irvng-wav Please, download the latest master, add this line
Environment="LOG=DEBUG"at the end of fileasus_numberpad_driver.wayland.serviceand install & reboot, and post the clean error log here again.
At the end of [Service] or [Install]?
from asus-numberpad-driver.
ldrahnik
commented on August 15, 2024
Service
from asus-numberpad-driver.
irvng-wav
commented on August 15, 2024
Ok, this time it worked great right after rebooting! Here's the current error.log:
error.log
from asus-numberpad-driver.
ldrahnik
commented on August 15, 2024
@irvng-wav Can I understand that you found nothing wrong?
from asus-numberpad-driver.
ldrahnik
commented on August 15, 2024
@irvng-wav Yes, create another issue please, thank you.
from asus-numberpad-driver.
ldrahnik
commented on August 15, 2024
@irvng-wav With the latest commit should be fixed setting up full brightness when is the laptop started.
from asus-numberpad-driver.
Related Issues (20)
- [Bug]: Numberpad instantly turns off on latest Fedora KDE Spin HOT 37
- ASUS Zenbook 14 UX3405MA_UX3405MA HOT 2
- [Bug]: layout not detected
- [Layout Request] ux7602-unicode HOT 7
- [Bug]: can not toggle numpad to touchpad HOT 39
- [Feature Request] Missing support for the 2023 asus GX650 and upper versions HOT 24
- [Layout Request] UX425QA HOT 3
- [Layout Request] GX650PZ HOT 10
- [Feature Request] Use events/signals to detect numlock key press HOT 12
- [Bug]: ERROR Numpad layout *.py from dir layouts is required as first argument HOT 3
- [Bug]: Script numberpad.py execution failed HOT 11
- [Feature Request] Fewer gestures for activating the calculator toggle HOT 1
- [Feature Request] Improvement of slide gestures activation area HOT 1
- [Feature Request] Gentoo support HOT 2
- [Layout Request] G512LU HOT 5
- [Bug]: Calculator key does not show the calculator HOT 13
- [Bug]: Driver doesn't start without GDM. HOT 31
- [Bug]: Wont launch anything/Install error? HOT 6
- [Bug]: Top buttons don't work and numbers don't match HOT 16
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from asus-numberpad-driver.