LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   sysvinit-scripts-2.0-noarch-9+: frozen mouse and keyboard in X (http://www.linuxquestions.org/questions/slackware-14/sysvinit-scripts-2-0-noarch-9-frozen-mouse-and-keyboard-in-x-4175426942/)

burdi01 09-12-2012 03:13 PM

sysvinit-scripts-2.0-noarch-9+: frozen mouse and keyboard in X
 
With sysvinit-scripts-2.0-noarch-9 and 10 I have a completely frozen mouse and keyboard in X. The only thing I can do is telnet in from an other box and reboot.

By applying one change after another I could narrow the problem down to this rc.M phrase:

Before:
======
Code:

# If we are returning from single-user mode we will need to restart
# udevd on systems that use udev:
if grep -wq sysfs /proc/mounts && grep -q tmpfs /proc/filesystems ; then
  if ! grep -wq nohotplug /proc/cmdline ; then
    if [ -x /etc/rc.d/rc.udev ]; then
      /bin/sh /etc/rc.d/rc.udev start
    fi
  fi
fi

After:
=====
Code:

# If we are returning from single-user mode we will need to restart
# udevd on systems that use udev:
if [ "$(/sbin/runlevel | cut -d ' ' -f 1)" == "1" ]; then
  if grep -wq sysfs /proc/mounts && grep -q tmpfs /proc/filesystems ; then
    if ! grep -wq nohotplug /proc/cmdline ; then
      if [ -x /etc/rc.d/rc.udev ]; then
        /bin/sh /etc/rc.d/rc.udev start
      fi
    fi
  fi
fi

At system startup the "before" code executes a "udevadm trigger --action= change", whereas the "after" code does not.
:(

volkerdi 09-12-2012 03:47 PM

Quote:

Originally Posted by burdi01 (Post 4778826)
At system startup the "before" code executes a "udevadm trigger --action= change", whereas the "after" code does not.
:(

Hmmm... it's looking like the bug before was in the comment, not the code. Thanks!


All times are GMT -5. The time now is 05:13 PM.