Ok... as for the root thing. Half the reason Linux is so secure (besides bugs being found and fixed quickly) is the user privilage system. If your running your system as an unprivilaged (not root) user and you execute some misconfigured or harmfull code it can only run with your permissions. Meening, it wont be able to harm your system.
On the other hand using root to do everyday tasks meens you run the risk of executing harmfull code with root permissions. Root permsissions meens it could overwrite remove any file on your system.
Thats a very simple explination, but you get my drift.
What to do? Create an everyday user account and use this account well, everyday. When you need to do something as root, su to root, or issue a sudo.
What su and [/i]sudo[/i]?
su (switch user) will quickly log you into another user. You can then execute what it is you need to and type exit to go back to your everyday user. su (with no argument) will default to the root user. eg;
[thorpe@ob] $ su
password? ********
[root@ob] # vim /etc/hosts.conf
[root@ob] # exit
[thorpe@ob] $
Notice it prompts for a password.
sudo is much the same, but instead of logging you into another account, it accepts a command as its argument, and it executes that command as root. eg;
[thorpe@ob] $ sudo vim /etc/hosts
You may need to install and configure them, but they are what I would consider essential tools.
As for those errors. They dont seem to serious if things are still working. Often you see more errors when calling things from a term. However if your like me you'll eventually want to iron out these little bugs.
Both those errors refer to some libraries that Im not familiar with. Panga seems to be a GTK libarary used by gedit, while QObject is a QT library used by kate. GTK and QT are both used to make windowed (is that a word?) or desktop type applications.
Really... if these errors bother you, you'll need to google some solutions. If not... I wouldn't worry too much.
