"synaptics" module missing, causing xorg not to start
Efficient, Rock Stable Operating System
Brought to you by:
q4osteam
Menu
▾
▴
#101 "synaptics" module missing, causing xorg not to start
When I put a copy of Q4OS Trinity Live 3.9 on a USB stick and booted in, it took quite a while until I got kicked off to the command line, checking xorg logs reveal that the trackpad on my laptop is the problem, saying that the synaptics module is missing.
Discussion
Anonymous
Here are my tdm.log and Xorg.0.log files.
On the other note the laptop has issues with Linux 4.x and Xorg, the TDM log tells me that it was taking so long to start Xorg that it even timed out.
Please try to install Synaptics driver:
$ sudo apt install xserver-xorg-input-synaptics
reboot and post a result.
Sorry I can't install Q4OS Trinity 3.9 using the Live image, because of the fact that my laptop has issues with Kernel 4.x making Xorg very slow, and the fact I can't boot into the desktop
You only need the command line, no Xorg required. You could try to install Q4OS from the install CD and then to run in Q4OS terminal:
$ sudo apt update
$ sudo apt install xserver-xorg-input-synaptics
and reboot. We are not able to reproduce the issue, so we would appreciate a report in order to investigate it.
EDIT: Edited as the live CD is unusable for installation.
Last edit: Q4OS Team 2019-11-28
I have installed Q4OS using the install image, I had to install latest kernel from backports and I installed the synaptics driver.
Does desktop start correctly after backports kenel installing ? Or does it start after the synaptics driver installation ? Would you provide Xorg.log please ?
It starts up after installing backports, because the laptop had issues running Debian 10 when it was in testing due to kernel version being a 4.x one, and TDM just straight up kills Xorg when it takes so long to start up.
Thanks, so missing Synaptics module doesn't seem to be the culprit, more likely a kernel video driver.
Closing this bug, as it's most likely not related to Synaptics driver as specified in the OP. You can opend a new bug, if relevant. A brief hardware specification is needed in such case.