Solution for MX Player not working after android 4.4.3 upgrading


I just installed Android 4.4.3 on my nexus 4, and sadly MX Player does not support this android version.

Problem:

image

Solution:
  Just go to play store And update your mx player. That’s all. Now your mx player will work as well as before. 💪

image

image

PS: Before reporting issue,  just check for latest updates in play store. We usually disable the “auto update”.  Update manually for latest release ❇:)

Advertisements

How to take screenshots in Nexus 4


Take a screenshot:
    There are times when you just want to capture what’s on your phone’s screen, so you can keep a record of it or show it to others at a later date, and thankfully this functionality comes baked into Android these days.
In nexus 4 we can do this by “Simply hold the Volume Down and Power buttons at the same time”.

That’s it.: -)

Reset your MYSQL Password


Hi friends,

After long time, today i thought of use my MYSQL db, But the thing is i’ve forget my password 😦  Then i asked to my friend mani, “pls help me mani, i ve to reset my MYSQL password urgently. He gave the simple solution”. 🙂

Here the i’m posting the simple steps to reset the mysql root password.

Open your terminal and type the following commands.

First we’ve to stop the mysql service,

  $ sudo service mysqld stop
 $ sudo mysqld_safe --skip-grant-tables

( It runs the mysql in safe mode and the “skip-grant-tables ” skips the table which ‘ve the MYQSL  user passwords )

The above command ‘ll start mysql server, now open a another tab in ur terminal and type this command.

$  mysql --user=root mysql  ( It 'll login as root without password)

Now type the below query in myqsl prompt.

Note: change “new-password” to your new password.  🙂

> update user set Password=PASSWORD('new-password') WHERE User='root';

That’s all     ve fun 🙂

ssh: WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!


Hi friends,

Today i faced a different problem on “ssh” connection. When i tried to connect a machine with mine, a new problem arrived. 😉 It’s look like the following,

[suresh@mercury ~]$ ssh rajee@192.168.1.7
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the RSA host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
25:e5:2b:dd:98:df:c8:f6:36:28:10:3d:c3:93:83:b0.
Please contact your system administrator.
Add correct host key in /home/suresh/.ssh/known_hosts to get
rid of this message.
Offending key in /home/suresh/.ssh/known_hosts:5
RSA host key for 192.168.1.7 has changed and you have requested
strict checking.
Host key verification failed.

The Solution is very simple. Just rename your “.ssh” into “.ssh_old” by using “mv” command.

Ex:

$ mv .ssh .ssh_old

Or just go to “.ssh” directory, and  edit the file name called “known_hosts”. In this file contains, which you already connected machine’s with your’s, public ssh keys . Now just remove the public key which ip address giving trouble.

Ex:

[suresh@mercury ~]$ cd .ssh
[suresh@mercury .ssh]$ ls
known_hosts
[suresh@mercury .ssh]$ cat known_hosts
192.168.1.7 ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDFZ5W
Dc0VUPae3hL7oWJg35NftAb804U/75vGY5tcffI2+7EeKWAPLWcXQJa9
+TD1q8KhYJjjpgB7Nx3tgl1JCM1Eti6jSFJZwAJKDXWrJqxy/loFq05EM9va9v
QM6sNOpYu8jng8OBXv79s1HoBrtIMUm4ivvqB3yTevYJeTtUQsT/cZRbaelOzmeh
O68xixQ2csUfrNAH//8JfemzsJV9B57+Ln6z/oc61ChdrMWCpwOtsCRMmG2pQsJZ4
xdr1axxlTPKQwblLmnbGLcUKjB4B/RSyjUH3OPLn2nj5KHqrOnbWRyuR1ElR5/x
wHFdbOXn4tkMwRrms6iuQKCitxB
[suresh@mercury .ssh]$

That’s all.

How to Disable the “SELinux” on Fedora 14


Hi friends,

If you want disable the “SElinux” on your linux box, Just follow the simple commands. 🙂

Open your terminal and login as root user, now we have to edit the “SELinux’s”
main configuration file.

$ gedit /etc/selinux/config

you will see some lines like this:

# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
# enforcing - SELinux security policy is enforced.
# permissive - SELinux prints warnings instead of enforcing.
# disabled - No SELinux policy is loaded.
SELINUX=enforcing
# SELINUXTYPE= can take one of these two values:
# targeted - Only targeted network daemons are protected.
# strict - Full SELinux protection.
SELINUXTYPE=targeted

Now, just change SELINUX=enforcing to SELINUX=disabled, like

SELINUX=disabled

and you’re done. You have to Reboot the machine to disable the SELinux.

That’s all. 

 

SELINUX=disabled

Solution for “ssh: connect to host localhost port 22: Connection refused”


Hi friends,

Since three days, i had problem with my ssh connection. When i was tried to connect my laptop to others machine,  I’m able to connect with them. But when i tried to connect, others machine to my laptop, I got this Error.

[student@mercury ~]$ ssh suresh@192.168.1.9
ssh: connect to host 192.168.1.9 port 22: Connection refused

Solution for this “port 22: Connection refused” :

First check if sshd is running by trying the command ‘$ pgrep sshd
on the host. If the output is empty, its very likely that sshd is not
running. Try ‘tail -f /var/log/messages’ on one terminal and do
a ‘$ /etc/init.d/sshd start‘ on another terminal.  Then, check the
output that comes up on the previous terminal.

 

if PID comes, like 1702(any number), we conform the “sshd” is running.

Next, we have to flush the “iptables” by using the following command,

$ sudo iptables -F

That’s all. Now you can connect with anyone via ssh.

If again the same problem appear, Try ‘$ grep sshd /var/log/messages | tail‘ and
$ grep ssh /var/log/secure | tail‘ and check for any possible issues.

🙂

 

ssh connection: port 22 problem


Hi friends,

Since today morning also i tried to learn about to “set up a centralized git repository”. I got many good links about this. But when i tried to do the “ssh”, i faced many obstacles. Then, i posted a mail to the “ILUGC” mailing list.(http://www.ae.iitm.ac.in/pipermail/ilugc/2011-March/065064.html) I got many suggestions/answers like,

* Disable the SElinx
* Flush the iptables using “$ iptables -F”
* nmap 192.168.1.9
* netstat -ltnp | grep 22

But still, i can’t resolve my problem. 😦  i’ve to “set up the centralized git up repo” At least by tomo