💾 Archived View for gemini.ctrl-c.club › ~phoebos › logs › kisslinux-2021-11-09.txt captured on 2024-05-26 at 16:12:23.
⬅️ Previous capture (2021-12-17)
-=-=-=-=-=-=-
[2021-11-09T05:23:31Z] <testuser[m]1> hi [2021-11-09T06:11:28Z] <CyberDucK> Hi [2021-11-09T06:12:38Z] <Guest55> Hi [2021-11-09T06:13:05Z] <CyberDucK> Anyone on? [2021-11-09T06:13:23Z] <CyberDucK> How do i autoload modules on boot? [2021-11-09T06:13:58Z] <CyberDucK> modules-load.d/*.conf method is not working [2021-11-09T06:16:09Z] <testuser[m]1> inittab or /etc/rc.d [2021-11-09T06:16:14Z] <testuser[m]1> check /etc/inittab [2021-11-09T06:30:35Z] <CyberDucK> Thanks a lot [2021-11-09T20:58:37Z] <jedavies> Anyone had an issue with sway after a recent update, where if you unplug then re-attach a keyboard/mouse then sway doesn't respond to the kbd/mouse at all? [2021-11-09T20:59:30Z] <jedavies> Noticed when switching between machines using a kvm switch, it's unresponsive when I switch back. [2021-11-09T22:21:06Z] <dilyn> are you sure it's sway and not a permission problem? [2021-11-09T22:41:50Z] <jedavies> sway and libseat were updated in the last week, could be either of them or maybe it was something unrelated I did myself. But I see it on 2 different machines/architectures. [2021-11-09T22:42:16Z] <jedavies> About a week ago it used to be that kvm switching to/from these machines was fine. Now I have to restart sway to get kbd/mouse working after doing that.