To have a quick summary of which installed packages on your system are not supported, install the debian-security-support :

[root@localhost:~#] apt-get install debian-security-support

A check for new unsupported packages is run everytime new packages are installed.

check-support-status utility can be run manually as well to get a list of all the unsupported packages installed on your system.

While using bash auto-completion feature, you may have the following error :
“bash : /usr/share/bash-completion/bash_completion : line 226 : syntax error near unexpected token ‘}'”

Make sure not to have any bash keywords like ‘do’, ‘done’ as an alias in your own bashrc file.
Rename your alias and reload your updated bashrc file. Auto-completion works fine now in your bash shell.

http://comments.gmane.org/gmane.comp.shells.bash.completion.devel/5145

http://stackoverflow.com/questions/22969050/bash-syntax-error-near-unexpected-token-done-with-alias-named-do

On Debian Jessie, I get this error while launching newsbeuter :

“XDG: configuration directory ‘/home/fool/.config/newsbeuter’ not accessible, using ‘/home/fool/.newsbeuter’ instead.”

XDG stands for X Desktop Group and now known as the freedesktop.org project.
More details about XDG

To fix it, here is the workaround :

fool@localhost:~$ cd /home/fool/.config/
fool@localhost:~$ ln -s ~/.newsbeuter/ newsbeuter

Once done, you might have another similar error :

“XDG: data directory ‘/home/fool/.local/share/newsbeuter’ not accessible, using ‘/home/fool/.newsbeuter’ instead.”

To fix it, here is the workaround :

fool@localhost:~$ cd /home/fool/.local/share/
fool@localhost:~$ ln -s ~/.newsbeuter/ newsbeuter

Hope this helps !

Here are a few tips to check the current version of the VMWare tools running in a Linux server and how to restart them if needed.

/usr/bin/vmware-toolbox-cmd

Beware of rejoining a Linux server to a Windows domain.
After restarting winbind service and rejoining a server running RHEL 6.6 within a Windows domain, the monitoring of this server and its services started to be a real mess, sending false alerts.
After investigation, new DNS entries were added. The DNS name was the same pointing to different IP addresses, the ones set up on the server.
By default, Samba enables all active interfaces except the loopback interface (whose IP address 127.0.0.1)
One solution is to specify the name of only one active interface.
This can be set up as follows :

/etc/samba/smb.conf

interfaces = eth0

If you are using the mail command line tool, this error “Cannot append message: Conflict with previous locker” can occur if a mbox.lock file is already here in your home directory. If you quit the mail program, make sure there is no more mbox.lock file by possibly deleting it.

Should you have the following error : “Puppet(err) : Could not retrieve catalog from remote server: Could not intern from pson:unexpected token in object at ”, the following steps helped me solving this problem :

On the Puppet master :

root@puppet_master:~# puppet node clean FQDN_node

On the host (represented here as FQDN_node) running Puppet agent :

root@puppet_agent:~# find /var/lib/puppet/ssl -type f -iname '*.pem' -exec rm -rf {} \;
root@puppet_agent:~# puppet agent -t --waitforcert=60 --server=FQDN_puppet_master

Should you have the following error : “Puppet(err) : Could not retrieve catalog from remote server. Error 400 on SERVER:could not parse YAML data for node”, the following steps helped me solving this problem :

On the Puppet master :

root@puppetmaster:~# rm /var/lib/puppet/yaml/node/FQDN_node
root@puppetmaster:~# rm /var/lib/puppet/yaml/facts/FQDN_node

On the host (represented here as FQDN_node) running Puppet agent :

root@puppet_agent:~# service puppet stop
root@puppet_agent:~# puppet agent --test --server FQDN_puppet_master

If you find yourself with Bluetooth blocked or disabled, use the rfkill command to reset the Bluetooth fonctionality.
rfkill package must be installed on your system to run the following commands below :

rfkill list
0: hp-wifi: Wireless LAN
Soft blocked: yes
Hard blocked: no
1: hp-bluetooth: Bluetooth
Soft blocked: yes
Hard blocked: no
2: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no

rfkill unblock 1

rfkill list
0: hp-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
1: hp-bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
2: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
3: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no

As a precaution, restart the Bluetooth service as follows :

service bluetooth restart
[ ok ] Stopping bluetooth: rfcomm /usr/sbin/bluetoothd.
[ ok ] Starting bluetooth: bluetoothd rfcomm.

Thanks for this tip here: Cannot enable Bluetooth anymore

Here is a very interesting article about monitoring battery capacity with Debian :

Different ways to monitor battery capacity with Debian

More information about IBAM, the Intelligent Battery Monitor