Ubuntu 14.04 preseed/late_command doesn’t work: this is why

The reason why

d-i preseed/late_command string

doesn’t work on your installation of Ubuntu 14.04 is that you are probably using Ubiquity.
I spent several hours trying to figure this out and at the end I managed to understand (thanks to http://askubuntu.com/questions/104135/preseed-late-command-not-running) that instead I (and you while you are here) should use this command:

ubiquity ubiquity/success_command string \

This last made my installation completely work.

Hope this will help others out there.


Incoming search terms:

  • preseed late_command (1)
  • preseed/late_command ubuntu (1)
(Visited 2,455 times, 1 visits today)

Asus X202E touchpad sensitivity with Ubuntu

The ones out there who decided to drop Windows 8 in favor of Ubuntu after buying an Asus X202E will probably face the issue of a too sensitive touchpad which makes the laptop barely usable, with a lot of random unwanted clicks especially during the “two finger scrolling”. The two finger scrolling is a feature I really don’t want to give up as well as the touch to click one, as i find them really convenient as long as I have to use the laptop as laptop, which means without an external pointing device such as a mouse.

First step to get to the desired settings is to check which hardware are we using.

As reported at this url http://superuser.com/questions/229839/reduce-laptop-touch-pad-sensitivity-in-ubuntu the best is to run the command:

xinput list

This will return the list of the input devices used by X (for a complete man page, refer to this : Xinput man page in a new tab)

From the list returned it will be easy to guess which is the touchpad device, in the Asus X202E it is:

ETPS/2 Elantech Touchpad (debian wiki here)

Since the laptop is equipped with a touchscreen display, do not confuse the touchpad with the digitizer of the display (Atmel Atmel maXTouch Digitizer).

Now we can easily get the initial parameter of the touchpad so we can tinker with them and the worst of the cases we can use them to revert the settings to the initial state.

To do this, to read the setting we are currently running with, the command to be issued is:

 xinput list-props "ETPS/2 Elantech Touchpad" | grep -i finger

This will return a few lines:

Synaptics Finger (289): 1, 1, 0
Synaptics Two-Finger Pressure (295): 282
Synaptics Two-Finger Width (296): 7
Synaptics Two-Finger Scrolling (299): 1, 1

We are going to tinker with the first parameter, “Synaptic Finger” in order to require much more pressure of the finger for the touchpad to become active.

what I type is:

sudo xinput set-prop "ETPS/2 Elantech Touchpad" "Synaptics Finger" 5 20 0

Where the second parameter (30) is the one used as threshold for the measured finger pressure. The first one seems to be the one used as “Release pressure” to measure the act of clicking.

I hope this short guide will be useful for other out there.

Final tip:

This settings will be gone after next reboot, so the best is to create a bash script and make it being executed at your login as suggested on this page: http://www.mepis.org/docs/en/index.php?title=Configuring_the_touchpad_with_xinput

so let’s create a script called touchpad.sh

sudo xinput set-prop "ETPS/2 Elantech Touchpad" "Synaptics Finger" 5 20 0

Let’s make it executable with:

chmod 755 touchpad.sh

You conveniently save it under a easily accessible folder like /usr/bin

then, if ou use Gnome 2or 3 like me, it’s sufficient to do as reported on this page http://stackoverflow.com/questions/8247706/start-script-when-gnome-starts-up you can open the terminal and type:


Using the graphical interface you can set it up and look for the script by just browsing the filesystem.

useful info here as well: https://help.ubuntu.com/community/SynapticsTouchpad

Enjoy your new configured touchpad.

asus x202e

Incoming search terms:

  • asus e202 linux (1)
  • asus e202 touchpad ubuntu (1)
  • asus yg fingerin (1)
  • kursor asus e202 tidak terbaca (1)
  • ubuntu touchpad sensitivity (1)
  • ubuntu タッチパッド 感度 (1)
  • لسبكس (1)
(Visited 3,293 times, 1 visits today)

Ubuntu Xinput man page

xinput – utility to configure and test X input devices


xinput(1) General Commands Manual xinput(1)


xinput – utility to configure and test X input devices
xinput is a utility to list available input devices, query information about a
device and change input device settings.

Test if the X Input extension is available and return the version num‐
ber of the program and the version supported by the server. This
option does not require a device name.

–list [–short || –long || –name-only || –id-only] [device]
If no argument is given list all the input devices. If an argument is
given, show all the features of device. If –long is provided, the
output includes detailed information about the capabilities of each
devices. Otherwise, or if –short is provided, only the device names
and some minimal information is listed. If –name-only is provided,
the output is limited to the device names. One device name is listed
per line. Note that the order the devices are listed is undefined. If
–id-only is provided, the output is limited to the device IDs. One
device ID is listed per line. Note that the order the devices are
listed is undefined.

–get-feedbacks device
Display the feedbacks of device.

–set-pointer device
Switch device in core pointer. This option does nothing on X servers
1.5 and later.

–set-mode device ABSOLUTE|RELATIVE
Change the mode of device.

–set-ptr-feedback device threshold num denom
Change the pointer acceleration (or feedback) parameters of device.
The xset(1) man page has more details. For X.Org Server 1.7 and above,
there are additional device properties pertaining to pointer accelera‐
tion. These do not replace, but complement the pointer feedback set‐

–set-integer-feedback device index value
Change the value of an integer feedback of device.

–set-button-map device map_button_1 [map_button_2 […]]
Change the button mapping of device. The buttons are specified in
physical order (starting with button 1) and are mapped to the logical
button provided. 0 disables a button. The default button mapping for a
device is 1 2 3 4 5 6 etc.

–query-state device
Query the device state.

–list-props device [device […]]
Lists properties that can be set for the given device(s).

–set-int-prop device property format value
Sets an integer property for the device. Appropriate values for for‐
mat are 8, 16, or 32, depending on the property. Deprecated, use
–set-prop instead.

–set-float-prop device property value
Sets a float property for the device. Deprecated, use –set-prop

–set-prop [–type=atom|float|int] [–format=8|16|32] device property value
Set the property to the given value(s). If not specified, the format
and type of the property are left as-is. The arguments are inter‐
preted according to the property type.

–watch-props device
Prints to standard out when property changes occur.

–delete-prop device property
Delete the property from the device.

–test [-proximity] device
Register all extended events from device and enter an endless loop
displaying events received. If the -proximity is given, ProximityIn
and ProximityOut are registered.

–test-xi2 [device]
Register for a number of XI2 events and display them. If a device is
given, only events on this device are displayed.

–create-master prefix [sendCore] [enable]
Create a new pair of master devices on an XI2-enabled server with the
given prefix. The server will create one master pointer named “prefix
pointer” and one master keyboard named “prefix keyboard”. If sendCore
is 1, this pair of master devices is set to send core events
(default). If enable is 1, this master device pair will be enabled
immediately (default).

–remove-master master [Floating|AttachToMaster] [returnPointer] [returnKey‐
Remove master and its paired master device. Attached slave devices
are set floating if Floating is specified or the argument is omitted.
If the second argument is AttachToMaster, returnPointer specifies the
master pointer to attach all slave pointers to and returnKeyboard
specifies the master keyboard to attach all slave keyboards to.

–reattach slave master
Reattach slave to master.

–float slave
Remove slave from its current master device.

–set-cp window master
Set the ClientPointer for the client owning window to master. master
must specify a master pointer.

–map-to-output device crtc
Restricts the movements of the absolute device to the RandR crtc. The
output name must match a currently connected output (see xrandr(1)).
If the NVIDIA binary driver is detected or RandR 1.2 or later is not
available, a Xinerama output may be specified as “HEAD-N”, with N
being the Xinerama screen number. This option has no effect on rela‐
tive devices.

–enable device
Enable the device. This call is equivalent to xinput –set-prop device
“Device Enabled” 1

–disable device
Disable the device. This call is equivalent to xinput –set-prop
device “Device Enabled” 0

device can be the device name as a string or the XID of the device.

slave can be the device name as a string or the XID of a slave device.

master can be the device name as a string or the XID of a master device.

property can be the property as a string or the Atom value.

X(7), xset(1), xrandr(1)

Copyright 1996,1997, Frederic Lepied.

Copyright 2007, Peter Hutterer.

Copyright 2008, Philip Langdale.

Copyright 2009-2011, Red Hat, Inc.
Peter Hutterer <peter.hutterer@who-t.net>
Philip Langdale, <philipl@alumni.utexas.net>
Frederic Lepied, France <Frederic.Lepied@sugix.frmug.org>
Julien Cristau <jcristau@debian.org>
Thomas Jaeger <ThJaeger@gmail.com>
and more.


X Version 11 xinput 1.6.0 xinput(1)

(Visited 1,080 times, 1 visits today)

Ubuntu & Debian FIX java plugin for Firefox and Chrome

friends_dont_let_friends_windows_mugHow to Fix java plugin in Ubuntu for Firefox/Chrome

The error:

Your browser Mozilla Firefox or Google Chrome refuses to execute a java applet because of the security risks related to an old version of java, most likely the jdk1.7.0_40 which has been disabled by Mozilla Firefox plugin mantainers on October the 16th. So you probably want to install jdk1.7.0_45.  Anyway, this said, this procedure will most likely work with following versions of Java, Firefox, Chrome, Ubuntu 🙂 And of course. if you need to install Java for your browsers or operating system and you haven’t yet installed once, just skip the parts with the “rm” command as the rest is the same.

Download and install the Jdk

First of all download the latest version of java from the oracle website:

from this page http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html , download either jdk-7u45-linux-x64.tar.gz OR jdk-7u45-linux-i586.tar.gz; which one of the two versions depends on your operating system.

Once the download finishes extract the folder in /usr/lib/jvm so you obtain /usr/lib/jvm/jdk1.7.0_45/jre/bin/java. The Java binaries folder is linked so developers can quickly switch between several versions. What we are doing here, will not affect the operating system use of java, if you want to use the new version of java in your operating system, then you’ll find some instructions at the end of this post.

Firefox, Chrome:

Usually you are tempted to use the folder in ~/.mozilla, I tried, it doesn’t seem to affect any way nor Firefox, nor Chrome. The clue is to use /usr/lib/mozilla/plugins/ so Google Chrome will be able to use this plugin as well. What we need to do, if you already have an old version of java, is to remove the link called libnpjp2.so. to do so move to the directory:

cd /usr/lib/mozilla/plugins/

As you can see a link to java is already there, but it is outdated:

 lrwxrwxrwx 1 root root 50 okt 22 22:03 libnpjp2.so -> /usr/lib/jvm/jdk1.7.0_40/jre/lib/amd64/libnpjp2.so*

Remove the link with the command:

 sudo rm -f libnpjp2.so

Then we can create a new link pointing to the new downloaded java in /usr/lib/jvm/jdk1.7.0_45/jre/lib/amd64/libnpjp2.so with the command:

ln -s /usr/lib/jvm/jdk1.7.0_45/jre/lib/amd64/libnpjp2.so

Restart Mozilla Firefox or Google Chrome and that’s all!
enjoy your up to date java plugin for Mozilla Firefox or Google Chrome.



P.s. Fixing java for your operating system

As i wrote before, the version of java picked up by the operating system in order to execute java code depends on the symbolic link in /etc/alternatives

Just check which version of java is picked up before changing it typing:

java -version

you should get something like:

java version "1.7.0_40"
Java(TM) SE Runtime Environment (build 1.7.0_40-b43)
Java HotSpot(TM) 64-Bit Server VM (build 24.0-b56, mixed mode)

Now, just remove the link in /etc/alternatives and replace it with a new one pointing to the new downloaded java in /usr/lib/jvm, like this:

cd /etc/alternatives
sudo rm -f java
ln -s /usr/lib/jvm/jdk1.7.0_45/jre/bin/java java

Then try to check again which version of java is in use now:

java -version
java version "1.7.0_45"
Java(TM) SE Runtime Environment (build 1.7.0_45-b18)
Java HotSpot(TM) 64-Bit Server VM (build 24.45-b08, mixed mode)


Yeeee, the new version is picked up now.

If you have problem just drop me a comment.



Incoming search terms:

  • jdk1 7 0_40#spf=1 (1)
  • membperbaiki fire fox di debian (1)
  • wtyczki java (1)
(Visited 3,833 times, 1 visits today)