A PCRE internal error occured. This might be caused by a faulty plugin

====== Differences ====== This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
tricks:mxmouse [2013/12/31 01:17]
admin [Logitech Mouse & Keyboard]
tricks:mxmouse [2016/12/04 03:17] (current)
admin [Albert]
Line 30: Line 30:
 I'm about to say: YES! I'm about to say: YES!
  
-==== Unifying Receiver ==== +===== Solaar (Logitech ​Unifying Receiver) ===== 
-Although Logitech doesn'​t offer a genuine Linux driver for it's Unifying Receiver devices, the community ​+Although Logitech doesn'​t offer a genuine Linux driver for it's Unifying Receiver devices, the community ​mitigates this problem, specificaly the [[http://​pwr.github.io/​Solaar/​index.html|Solaar Project]] brings a fully functional solution to using such devices on your Linux machines. 
 + 
 +Normaly the logitech-djreceiver driver should already be enabled and loaded, you can check on that by typing viewing dmesg right after pluging in the unifying receiver, it should output something like: 
 +<​code>​ 
 +dmesg 
 +[21449.244283] usb 1-1.1.2: new full-speed USB device number 11 using ehci-pci 
 +[21449.357947] usb 1-1.1.2: New USB device found, idVendor=046d,​ idProduct=c52b 
 +[21449.357955] usb 1-1.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 
 +[21449.357959] usb 1-1.1.2: Product: USB Receiver 
 +[21449.357962] usb 1-1.1.2: Manufacturer:​ Logitech 
 +[21449.368092] logitech-djreceiver 0003:​046D:​C52B.000F:​ hiddev0,​hidraw5:​ USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:​00:​04.1-1.1.2/​input2 
 +[21449.371256] input: Logitech Unifying Device. Wireless PID:101a as /​devices/​pci0000:​00/​0000:​00:​04.1/​usb1/​1-1/​1-1.1/​1-1.1.2/​1-1.1.2:​1.2/​0003:​046D:​C52B.000F/​input/​input18 
 +[21449.371521] logitech-djdevice 0003:​046D:​C52B.0010:​ input,​hidraw6:​ USB HID v1.11 Mouse [Logitech Unifying Device. Wireless PID:101a] on usb-0000:​00:​04.1-1.1.2:​1 
 +</​code>​ 
 + 
 +Also, the udev package must be installed and the daemon running, which is probably the case since it's the /dev/ and hotplug management daemon... You'd already have noticed if it wasn't there ;-) 
 + 
 +Create a file solaar.list in /​etc/​apt/​sources.list.d/,​ with the following contents: 
 +<​code>​ 
 +sudo nano /​etc/​apt/​sources.list.d/​solaar.list 
 + 
 +deb http://​pwr.github.io/​Solaar/​packages/​ ./ 
 +deb-src http://​pwr.github.io/​Solaar/​packages/​ ./ 
 +</​code>​ 
 + 
 +Then update your packages descriptions and install: 
 +<​code>​ 
 +sudo apt-get update 
 +sudo apt-get install solaar 
 +</​code>​ 
 + 
 +Solaar is now accessible through the "​Applications > Accessories"​ menu.\\ 
 +One noticable thing is that, at first, I blindly enabled the "​Smooth Scrolling"​ option that Solaar presented for my Performance MX Mouse. Just to discover that it made the //locked wheel// scrolling jump one page at a time and not allow any subtle scrolling movement anymore. Only the //free wheel// would allow me to, more or less, control the scrolling behavior. Un-checking that option brought me back to what I initialy expected from the scroll wheel. 
 +===== Easystrokes ===== 
 +As I stated earlier, my Logitech Performance MX mouse has 7 buttons... What the hell could I use them for? 
 + 
 +Download [[http://​sourceforge.net/​projects/​easystroke/​files/​easystroke/​|Easystrokes from sourceforge]].\\ 
 +Let's say we downloaded that archive to our ~/Downloads directory.\\ 
 +We need to extract the archive, install a few dependency libraries and make the application. Easy! 
 +<​code>​ 
 +cd ~/​Downloads/​ 
 +sudo apt-get install g++ libboost-serialization-dev libgtkmm-3.0-dev libxtst-dev libdbus-glib-1-dev intltool 
 +tar xzf easystroke-0.6.0.tar.gz  
 +cd easystroke-0.6.0/​ 
 +make install 
 +</​code>​ 
 + 
 +You should now find the Easystroke application uner "Menu > Applications > Universal Access > Easystroke"​ 
 + 
 +=== Easystroke usage === 
 +It wasn't immediately obvious for me to figure out how to use Easystroke. My first, simple, objective was how to "​map"​ the "thumb down" button of my mouse to an action. 
 + 
 +First off, while the Easystroke window is displayed, head over to the "​Preferences"​ tab and activate the "​Autostart easystroke"​ check box, so that Easystroke will always be active upon startup. Selecting "Show tray icon" is also interesting if you want a quick way to access the application from the menu. 
 + 
 +Additionally,​ you can also specify certain windows as “exceptions” and the mouse movements will not be recognized as gestures when working within those windows. Specifying an exception is easy, all you have to do is click on “Add Exception” and then on the window. It will then be added to the exception list. 
 + 
 +Next up, you need to create gestures and configure them to run custom commands. Go to the “Actions” tab, click on Add Action, provide your gesture with a name, click on type. You can then choose from amongst the different actions that you can perform with the gesture. You can run a command, send a keystroke, scroll a page and more. Then provide the detail for the type you chose. Click on “Record Stroke” and using the keys and mouse button you created above draw the stroke on the screen. That’s it you are done. The next time you draw a similar stroke again with Easystroke running the configured action will be executed automatically. 
 + 
 +===== Albert ===== 
 + 
 +One of the best invention next to the keyboard and mouse are the application launchers. They avoid you going through countless icons and windows to reach the application / folder / document that you're looking for. 
 + 
 +There are a few packages available that offer this kind of functionality,​ one of the first to go for would be [[https://​launchpad.net/​synapse-project|Synapse]] if we weren'​t going for [[https://​github.com/​ManuelSchneid3r/​albert/​wiki/​User-guide#​how-to-install-albert|Albert]]. 
 + 
 +Alternatives would also be [[http://​engla.github.io/​kupfer/​|Kupfer]] and [[http://​do.cooperteam.net/​|GnomeDo]]. 
 + 
 +=== Installing Albert === 
 + 
 +Kind of disappointing is that the [[https://​github.com/​ManuelSchneid3r/​albert/​wiki/​User-guide#​how-to-install-albert|Albert'​s GitHub page]] is only offering the //compile from source// option for Debian, thus LMDE2, systems. So we'll have to go that way... 
 + 
 +First we **make sure that we're using Qt version > 5.3**, as it is stated that below this Qt version there are known problems with Albert. 
 +<​Code>​ 
 +> qmake --version 
 +QMake version 3.0 
 +Using Qt version 5.3.2 in /​usr/​lib/​x86_64-linux-gnu 
 +</​Code>​ 
 + 
 +We'll also make sure all **required libraries** are available:​ 
 +<​Code>​ 
 +> sudo apt-get install g++ cmake qtbase5-dev libqt5x11extras5-dev libqt5svg5-dev libqt5sql5-sqlite libmuparser-dev 
 +</​Code>​ 
 + 
 +Then download the GitHub master version, put it in ''/​opt''​ and compile: 
 +<​Code>​ 
 +> sudo su 
 +Password: 
 +> cd /opt 
 +> wget https://​codeload.github.com/​ManuelSchneid3r/​albert/​zip/​master 
 +> unzip albert-master.zip 
 +> cd albert-master 
 +> cmake . -DCMAKE_INSTALL_PREFIX=/​usr -DCMAKE_BUILD_TYPE=Release 
 +> make [-j 6] 
 +> make install 
 +</​Code>​ 
 +**note:** the ''​-j 6''​ option is here to let make use multiple processors. This will greatly reduce compile time and should be tuned to your available cores of course.