You are not logged in.
Pages: 1
So I tried to configure my laptop so I can use the touchscreen (my laptop is Asus Zenbook) and a stylus. I use i3 manager, so I just installed evdev and everything started working (I can tap on the screen with my finger and it recognizes it). But when I try to use my stylus, the screen blinks once (becomes black and then everything appears again), and then instantly shutdowns. libinput debug-events shows me this before shutdown:
-event17 TABLET_TOOL_PROXIMITY +11.887s 148.24*/76.60* tilt:0.01*/0.01* pressure: 0.00* pen (0, id 0) proximity-in axes:ptbtn:S
event17 TABLET_TOOL_AXIS +11.893s 148.03*/76.68* tilt:0.01/0.01 pressure: 0.00 I cannot really work out how using my stylus can affect in shutting down the whole system, so I'd be grateful if anyone could help me.
Offline
Would you mind sharing a complete journal log of the affected boot?
Offline
Offline
The log ends with your machine going into hibernation, I had expected to see something indicating a shutdown or crash. Not sure why the Stylus would cause your system to hibernate.
Have you set up hibernation properly?
Other than that:
- I see you are booting the LTS kernel. Does it work when using the current linux package?
- Consider updating your system firmware (BIOS), there are several new releases for your machine.
Offline
I figured it out. The problem was in one of the suggestions on arch's wiki ('laptop' article):
/etc/udev/rules.d/99-lowbat.rules
# Suspend the system when battery level drops to 5% or lower
SUBSYSTEM=="power_supply", ATTR{status}=="Discharging", ATTR{capacity}=="[0-5]", RUN+="/usr/bin/systemctl hibernate"I had the same rule in my system, but for 2%. It appears that this rule somehow triggered when I used my stylus.
Anyway, thanks for help!
Offline
This explains why the pen would cause your system to hibernate. Good catch!
As is mentioned in the wiki, you can modify this rule if you have battery powered peripheral devices:
If you have more than one battery or if you are using a battery powered peripheral device, the rule could be triggered unexpectedly by another battery discharging; this can be fixed by checking /sys/class/power_supply/nameOfMainBattery/attributesAndOtherDirectories for another pair attribute/value to add to your udev rule. This further attribute must be specific to the main battery, for example model_name.
Offline
Pages: 1