Pidgin 2.10.7 was released and it brings numerous fixes, improvements, and a few new features, especially to MSN, Gadu-Gadu, MXit, Sametime, IRC and Yahoo! protocols.

All Pidgin users are urged to upgrade to the newly released 2.10.7 version as soon as possible, as it contains important security updates. Without any further ado, let’s take a look at the actual changes:

• Fixed an issue with the configure script, which will now exit with status 1 if an invalid protocol plugin is specified using the –with-dynamic-prpls and –with-static-prpls arguments;
• Fixes a libpurple crash related to UPnP responses with unusual long values;
• Repaired libpurple issue related to libgcrypt, when compiling with GnuTLS support;
• Fixed UPnP mappings on libpurple, for routers that return empty elements;
• The Tcl plugin for libpurple now uses race-free, saner plugin loading;
• The Tcl signals-test plugin has been fixed for savedstatus-changed in libpurple;
• Improved support for non-X11 GTK+, such as the one from MacPorts;
• Fixed a startup crash related to large contact lists on Gadu-Gadu accounts. Therefore, avatar support has been disabled until version 3.0.0);
• Implemented support for SASL authentication on IRC protocol;
• Topic setter info is now printed when joining an IRC channel;
• Fixed SSL certificate issues when signing into MSN accounts;
• Fixed a MSN crash when a user is removed before its avatar is loaded;
• Fixed a bug that could allow a remote MXit user to specify a local file path to be written to;
• Fixed a bug that could lead to remote code execution or a crash, because the MXit server could send specially crafted data;
• MXit farewell messages are now displayed in a different color;
• Added support for typing notification in MXit;
• Added support for the MXit Relationship Status profile attribute;
• Removed all MXit Hidden Number reference;
• When joining a MXit GroupChat or have a pending invite, other invites are being ignore now;
• Centered the buddy’s name vertically in the buddy-list for MXit protocol;
• Decoding of font-size changes in the markup of received messages has been fixed in MXit;
• The maximum file size that can be transferred on MXit is now 1 MB;
• MXit avatars are no longer downscaled to 96×96;
• Fixed a crash for the Sametime protocol, related to unusual long user IDs send by a malicious server;
• Fixed a double-free in picture/profile loading code for the Yahoo protocol;
• Server-side buddy aliases can now be retrieved on Yahoo accounts;
• Added support for sndio GStreamer backends to the Voice/Video Settings plugin;
• Fixed Contact Availability Detection plugin crash;
• Improved support for non-X11 GTK+, such as the one from MacPorts, on the Message Notification plugin.
You can  Download Pidgin 2.10.7 right now from Softpedia.

VirtualBox Commands List

Valic —  February 14, 2013 — 1 Comment

If you installed VirtualBox following this guide Run Virtual Machines and you are new to VirtualBox, then the following commands will help you to gather information and control your Virtual machines:

1. How to show the VirtualBox VM info:

root@debian:~# VBoxManage showvminfo

Where <vmname> is the name of your Virtual Machine

2. How to show the VM Harddrive info:

root@debian:~# VBoxManage showhdinfo

<filename> is the name of your .vdi file

3. How to list running VM:

root@debian:~# VBoxManage list runningvms

4. How to list available VM:

root@debian:~# VBoxManage list vms

5. How to list available VM Harddrives:

root@debian:~# VBoxManage list hdds

6. How to list all available ISO images:

root@debian:~# VBoxManage list dvds

7. How to Start a Virtual Machine:

Here you need to use the nohup command and add & to the end of command to run process in background so Virtual Machine will continue to run if you are closing the console. Continue Reading…

If you want to use windows 8 with Linux here is the solution.

If the Grub loader is not loading after windows 8 install, first you need to boot with a Live CD.

Then run these commands as root:

To find the drive where Linux is installed run the following command:

fdisk -l

Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1        9330    74936320   83  Linux

In my case sda1 is the drive where Linux is installed.
Then you need to run the following commands:

mount /dev/sda1 /mnt/
mount -o bind /dev /mnt/dev
mount -o bind /proc /mnt/proc
cp /proc/mounts /mnt/etc/mtab/
chroot /mnt /bin/bash
grub-install /dev/sda Continue Reading...

Few days ago I typed crontab -r instead of crontab -e. Well, my crontab was immediately deleted, without any warning. The first thing that I’ve done was to check if there was some backups on the server. As usual, there was no backups on my server.

So..If you accidentally type crontab -r instead of crontab -e , I have the solution for you:

In the system logs /var/logs/ are stored all crontab-calls of your system and you can easily extract them. Depending on your system you need to  cat and grep all crontab lines from the /var/log/syslog* files like this:

cat /var/log/syslog | grep -i "`which cron`" > cron_recovery_file

`which cron` will automatically be replaced by /usr/sbin/cron on Debian.

You need also extract all data from older messages logs stored as .gz archives:

gzip -d /var/log/syslog*.gz -c | grep -i "`which cron`" >> cron_recovery_file

In this moment you have a file called cron_recovery_file  that contains all your crontab-calls.

Your file will look like this now:

Feb 12 19:00:01 debian-tutorials /USR/SBIN/CRON[53198]: (root) CMD (crontab_command > /dev/null 2>&1)
Feb 12 19:00:01 debian-tutorials /USR/SBIN/CRON[53199]: (root) CMD (/scripts/backups > /dev/null 2>&1)
Feb 12 19:00:01 debian-tutorials /USR/SBIN/CRON[53200]: (root) CMD (mysql -u root --password=************ -e "flush query cache"; > /dev/null 2>&1)
Feb 12 19:09:01 debian-tutorials /USR/SBIN/CRON[53277]: (root) CMD (  [ -x /usr/lib/php5/maxlifetime ] && [ -d /var/lib/php5 ] && find /var/lib/php5/ -type f -cmin +$(/usr/lib/php5/maxlifetime) -print0 | xargs -n 200 -r -0 rm)
Feb 12 19:17:01 debian-tutorials /USR/SBIN/CRON[53288]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Feb 12 19:30:01 debian-tutorials /USR/SBIN/CRON[53293]: (root) CMD (another_crontab_command > /dev/null 2>&1)

Now, you need to start with the first line and copy/paste the call ( denotes the stuff in the brackets after ‘CMD’) to a new textfile which will be your new crontab. Continue Reading…

In this article I will show you some MySQL commands with examples.

1. MySQL Set Root Password

You can set the mysql root password from command line like this:

mysqladmin -u root password your_password

You can also change mysql root password if you forgot it using this tutorial: How to Recover MySQL Root Password

2. Change MySQL Users Passwords from the command line

mysqladmin -u mysql_username -h mysql_host -p password 'new_mysql_password'

3. How To Connect to Local MySQL Server

This is how you connect to your local MySQL server from the command line:

mysql -u root -p

4. Create a MySQL Database

The following command will create a new MySQL database after you are connected:

create database debiantutorials_db;

5. Backup MySQL Database with mysqldump

Backup a database to a .sql file:

mysqldump -u root -p debiantutorials_db > debiantutorials_db.sql

You can also compress the database with gzip on the fly while you are dumping:

mysqldump -u root -p debiantutorials_db | gzip -v > debiantutorials_db.sql.gz

6. Mysqldump and Skip Table

You want to dump a mysql database with one or more crashed tables and you get an error like this? Continue Reading…