Forum › Forums › Official Releases › antiX-21/22 “Grup Yorum” › keyboard & mouse stopped working
- This topic has 30 replies, 11 voices, and was last updated Jan 1-3:24 pm by kbJFJF4fSzoJZw.
-
AuthorPosts
-
November 24, 2021 at 12:01 am #71621Member
ex_Koo
After this morning updates my mouse a keyboard have stopped working.
November 24, 2021 at 12:49 am #71622Moderator
christophe
::I assume your signature line is stating the kernel & version (sysvinit), right?
(Just noting – I’m having no problems with antiX kernels.)
confirmed antiX frugaler, since 2019
November 24, 2021 at 5:38 am #71628Memberex_Koo
::Thanks for your reply
Been running the liquorix kernel the whole time I updated to that version a few days ago, was working fine until this morning updates.
Shame really was enjoying 21 have been using it as my main for the late week. Tried boot to other versions still the same, I can always use the disk space for something else. ThanksNovember 24, 2021 at 7:21 am #71629Member
Xecure
::Koo, you are an experienced user, so we don’t need to give too many instructions.
Please, chroot into your installed antiX system (from a live USB or from a different installed system) and please share with us the las update information in /var/log/apt/history, so we can try to figure out which update is to blame.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.November 24, 2021 at 3:27 pm #71662Memberex_Koo
::@Xecure I uploaded as a text file. Was complaining about spam.
Thanks
Attachments:
November 24, 2021 at 6:32 pm #71672Member
Xecure
::From this list, the suspicious ones should be:
xserver-xorg-core libblockdev-fs2 libdbus-1-3 libsmbclient dbus-x11 xserver-common libuuid1 libblockdev2 libblockdev-part-err2 libblockdev-utils2 libpolkit-gobject-1-0 libprocps8 procps rfkill dbusI don’t think the ones related to filesystems and mounting should be touching input devices.
rfkill should only be related if the devices are wireless, but this shouldn’t be blocking automatically wireless connection.
dbus and xorg are the most suspicious, but I cannot see any package related to input either, only common and core packages.If it was some libinput or libevdev, then we could point out that these are to blame, but I cannot see them there.
Does anyone know if policykit can manage or control permissions to input devices?
antiX Live system enthusiast.
General Live Boot Parameters for antiX.November 24, 2021 at 11:32 pm #71698Memberex_Koo
::@Xecure
I will try over the next few days to work this out it must be something simple. Just a bit busy with house Reno’s at the moment.Thanks for replying.
November 27, 2021 at 10:54 am #71794MemberModdIt
::I think I am also being affected with this, desktop seems frozen, maybe just no input possible.
AntiX21 Runit 64 Bit. the problem is most apparent in latest kernel but still occurs when booted with the older one.
The base system still runs, printing a big job just continued until finished. The printer is USB connected so
it does not look port related.Have to kill with power switch and reboot.
Also noticing constant disk activity, worrying for my ssd. Top shows Kworker doing something probable reason.The problem is also apparent on a start from live stick. Could not diagnose but looks like a service runs amok.
I have now been running a sysv init Live setup on same computer for hours without any issue.
Disk activity nil unless starting an application, working with mail, writer or browsing.November 27, 2021 at 1:52 pm #71807Memberex_Koo
::It is so strange the keyboard and mouse are live as if they are working but theirs no response. And the desktop is not locked up as my i3bar modules are still working.
Tried changing kernels but it was still the same, yet if you stay in tty the keyboard work fine.November 27, 2021 at 2:07 pm #71809Forum Admin
anticapitalista
::If you are running runit version, post output of
ls -la /etc/service/Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
November 27, 2021 at 8:23 pm #71822MemberModdIt
::I had first thought I had a hardware defect, now decided to start with a clean repeatable setup.
Test setup, A fresh download 64 bit runit full, sha256 is correct, fully updated, nothing is outside of antiX or antiX installer packages with exception of oracle Java. I did not install open java as it
throws an error. Want to be sure problems are not from some obscure open java bug.First I will run without Brother driver setup for a few hours, as long as my daughter does not need printouts that is. Then install my printers, my laser only needs a PPD not multiarch support like the Brother MFC.
Only things I have noticed during setup, connman is repeatedly looking for timeservers. DNS check showed connections to 8.8.8.8 google, Nazis love that, take away 2 dots and you have two Heil H greetings.
found using netstat.OFF Topic: How can I force a different DNS, is that hardcoded in connmann now.
At present disk is quiet, desktop ok.
November 27, 2021 at 11:50 pm #71826Memberex_Koo
::Will do it later.
- This reply was modified 1 year, 5 months ago by ex_Koo.
- This reply was modified 1 year, 5 months ago by ex_Koo.
November 29, 2021 at 3:29 am #71902Memberstevesr0
::(ADDED HERE TO HIGHLIGHT POSSIBLE CAUSE: conflict between xserver-xorg-core and xserver-xorg-video-modesetting? see my findings below for my Sid install.)
Hi all,
Maybe related problem, maybe not.
I am running a “minimal” install of Sid to which I have added X. All was running fine until after I did an apt update and full-upgrade tonight. Twenty-eight packages downloaded. One (libcodec2-1.0 (1.0.1-3) was labeled as an “automatic” install, the rest upgrades. The twenty-seven package upgrades included 11 libqt5 files, 9 libav files (including ffmpeg), 2 X files (xserver-xorg-core and xserver-common), 4 grub files(grub2-common, grub-common, grub-pc and grub-pc-bin) and libcrypt.
I boot into the command line and log in without problems. However, after launching x via startx, there is no response to the mouse or the trackpad and trying the “magic” keys does nothing to shut down the machine.
I will check for issues reported with the xserver update or other files in my 28 and repost if I discover a solution. Since others are reporting similar issues with recent updates, perhaps there is a common package that we share. If it would be helpful, the upgrades for the libav files are from 7.4.4.1-2 to 7.4.4.1-2+b1, the libqt5 files from 5.15.2+dfsg-13 to 5.15.2+dfsg-14, the grub files from 2.04-20 to 2.06-1, the xserver files from 2:1.20.13-2 to 2:1.20.13-2.0nosystemd1, libcrypt20 from 1.9.4-3+b1 to 1.9.4.4. Note that after installing libcodec2-1.0, libcodec2-0.9 was marked for autoremove.
Looking through the package dependencies and conflicts, I see that xserver-xorg-core, version 2:1.20.13-2.0nosystemd1, is listed as conflicting with the “provided xserver-xorg-video-modesetting”. This package is a virtual package.
If others confirm this, then it indicates that might be the cause of the problem — although it sounds a little crazy and (being a newbie) I am probably misinterpreting it.
Searching, I found older complaints of conflicts between the xserver-xorg-video-modesetting and xserver-xorg-core. I understand that currently this is actually provided by xserver-xorg-core. I note that in my antiX-19 system, the same conflict is reported, even though I am not having any problem with running x on this machine (which is what I am using to type this).
Well, if this is the problem for others, then I hope my report helps.
whether this is really the cause or not, I would appreciate advice on how to fix.
stevesr0
P.S. probably irrelevant, but I note that the libqt5 packages are a little ahead of the latest kernel available on Sid (5.15.2 vs 5.15.0.2). Is it possible that some of these require a non released 5.15.2 kernel?
- This reply was modified 1 year, 5 months ago by stevesr0.
November 29, 2021 at 5:07 am #71904Memberex_Koo
::I have had a nought of this site we are trying to solve a problem not bloody cause one.
A potentially unsafe operation has been detected in your request to this site
Your access to this service has been limited. (HTTP response code 403)
If you think you have been blocked in error, contact the owner of this site for assistance.
Block Technical Data
Block Reason: A potentially unsafe operation has been detected in your request to this site
Time: Mon, 29 Nov 2021 5:04:43 GMT
About WordfenceWordfence is a security plugin installed on over 4 million WordPress sites. The owner of this site is using Wordfence to manage access to their site.
You can also read the documentation to learn about Wordfence’s blocking tools, or visit wordfence.com to learn more about Wordfence.
Click here to learn more: Documentation
Generated by Wordfence at Mon, 29 Nov 2021 5:04:43 GMT.
Your computer’s time: Mon, 29 Nov 2021 05:05:02 GMT.November 29, 2021 at 5:09 am #71905Memberex_Koo
::Remove my membership now I wasted time I do not have to wasted heaps of typing for nothing..
-
AuthorPosts
- You must be logged in to reply to this topic.