I was trying to use Touchégg/Touché, but it wasn't working in Wayland. So, I decided to test Xorg instead. However, after switching to Xorg, I encountered a critical issue:
Both my keyboard and mouse worked on the login screen but stopped working immediately after logging in.
I tried checking Xorg log files, but they were missing.
To troubleshoot, I used Zorin Connect’s Remote Input to run a few commands and log out. However, this was painfully slow.
I also tried connecting an external mouse and keyboard, but they didn’t work either.
System Information
PC Model: Dell Inspiron 5558
8GB DDR3L RAM
1TB HardDisk (128GB alloted to Zorin)
Intel HD Graphics
Intel i5 4th Gen (U)
Operating System: Zorin Core 17 (Dual boot with Windows 10)
Xorg Version: x11
Wayland xinput list Output:
Xorg:
Custom udev Rule: I have a udev rule to disable the touchscreen, as it was clicking on its own. Reference: How to disable touchscreen (Wayland)
Additional Information
This is what ChatGPT suggested about the issue:
It looks like the Xorg log file is missing. Let's check where it's located and troubleshoot further.
1. Check if Xorg logs exist in alternative locations
Try running:
ls /var/log/Xorg*
or
ls ~/.local/share/xorg/
If a log file exists, open it with:
cat /var/log/Xorg.0.log | less
or
cat ~/.local/share/xorg/Xorg.0.log | less
2. Check if your system uses Wayland instead of Xorg
If you're running a Wayland session, Xorg logs won't exist. Run:
echo $XDG_SESSION_TYPE
If it returns wayland, then you're using Wayland, and Xorg logs won't be available.
3. Check if the Xorg service is running
If you're on Xorg, check the status with:
ps aux | grep Xorg
If there's no output, Xorg isn't running.
4. Check journal logs for input errors
Since system logs might still contain input device issues, run:
journalctl -b | grep -i input
This will show input-related logs from the current boot.
Let me know what you find!
Would appreciate any help in resolving this! Let me know if I should provide more details.