Logger "ACPI group/action undefined: $1 / $2" #xinput set-prop "SynPS/2 Synaptics TouchPad" 307 0 #xinput set-prop "SynPS/2 Synaptics TouchPad" 307 1 # Default acpi script that takes an entry for all actionsĮxport XAUTHORITY=`ls -1 /home/*/.Xauthority | head -n 1`Įxport DISPLAY=":`ls -1 /tmp/.X11-unix/ | sed -e s/^X//g | head -n 1`" Running xinput after the scripts have finished running shows the following missing % cat /etc/acpi/handler.sh It would seems xinput is not aware of the mouse despite the second script workaround as suggested in the original sources. ↳ Microsoft Natural® Ergonomic Keyboard 4000 id=10 ⎜ ↳ Microsoft Natural® Ergonomic Keyboard 4000 id=11
⎜ ↳ AlpsPS/2 ALPS DualPoint TouchPad id=15 I suggest you update the touchpad driver in device manager.
I am also using the latest stable version of udev (systemd) and xinput.Īny ideas what the problem occurs and how to fix this ? Has anything changed in udev regarding the way external programs are run (considering both the sources I cited are quite old) ? Is there any other way I can accomplish remapping of the buttons when it is plugged in? The cursor (cross-hairs) should now be aligned with the new specified angle (as seen below) You can work this way and Ortho will draw lines accurately lined up with this new angle, but you may start to tilt your neck or got sick of the way it looks. Running the script standalone works fine. The 3rd click specifies which side of the new X axis will the Y axis be facing.
Increasing the sleep duration does not help. The mouse is listed by xinput only after both scripts have finished. The problem is that despite calling the second script from inside the wrapper script, the mouse is still not listed by xinput. Xinput set-button-map $logitech_mouse_id 1 2 3 4 5 2 2 8 9 10 11 12 13 14 15 16Įcho "Xinput did not find Logitech mouse" > $LOG # Map button 6 (scroll wheel tilt-left button) and 7 (scroll wheel tilt-right button) to button 2 (middle button) This works in most cases, where the issue is originated due to a system corruption.
Number one – Shutdown, restart, and try again.Verbose logging can tell you a much more useful information.īack to the main topic of AutoCAD freezing up at startup. If the application has the ability to produce a. Of course this is just a simple scenario, but you get the idea. Probably the same type of thing was going on. When in fact, task B was successful and it’s task C that froze up. I recall many years ago, there was a bug in a certain program that would tell the user that there were licensing problems if the program crashed, when in fact this was not true at all. Now what message is the user looking at? The one about task B running. If your AutoCAD froze at this point, you might start looking for a problem with “acapp.arx”, but you might be barking up the wrong tree.Ĭonsider the following sequence of events. Also try the Selection tab and uncheck When no command is active under Selection Preview. In the image below, the message says “Loading plug-ins…acapp.arx”. If this doesnt improve the situation then go to Tools>Options (or type in Options at the command line) and on the Display tab uncheck the ‘Show rollover ToolTips’ option.
In recent versions of AutoCAD, a series of messages appear in the splash screen showing you the progress of the load. In many cases it’s not the fault of AutoCAD, it could be that the Internet connection is slow, or the A/V is blocking something, etc. Take AutoCAD for example, a frequent complaint about this application is that it starts up slowly and/or it hangs up during loading. In some cases you might receive feedback from an application that is misleading.