xsession and kde errors

Morroth · 07-11-2007, 09:44 AM

My system Arch Linux 2007.05 (Duke), kde 3.5.7 (kdemod).

My .xsession-errors directly on login in kde:

Code:

xset:  bad font path element (#76), possible causes are:
    Directory does not exist or has wrong permissions
    Directory missing fonts.dir
    Incorrect font server address or syntax
startkde: Starting up...
kbuildsycoca running...
<stdin>:0: warning: Unknown encoding: pl_PL
    kbuildsycoca running...
Reusing existing ksycoca
kbuildsycoca: WARNING: '/opt/kde/share/applications/kde/ark.desktop' specifies undefined mimetype/servicetype 'application/x-tbz2'
kbuildsycoca: WARNING: 'ark_part.desktop' specifies undefined mimetype/servicetype 'application/x-tbz2'
kbuildsycoca: WARNING: 'knotify.desktop' specifies undefined mimetype/servicetype 'KNotify'
kbuildsycoca: WARNING: '/usr/share/applications/wine.desktop' specifies undefined mimetype/servicetype 'application/x-ms-dos-executable'
kbuildsycoca: WARNING: '/usr/share/applications/wine.desktop' specifies undefined mimetype/servicetype 'application/x-msdownload'
kbuildsycoca: WARNING: '/usr/share/applications/wine.desktop' specifies undefined mimetype/servicetype 'application/exe'
kbuildsycoca: WARNING: '/usr/share/applications/wine.desktop' specifies undefined mimetype/servicetype 'application/x-exe'
kbuildsycoca: WARNING: '/usr/share/applications/wine.desktop' specifies undefined mimetype/servicetype 'application/dos-exe'
kbuildsycoca: WARNING: '/usr/share/applications/wine.desktop' specifies undefined mimetype/servicetype 'vms/exe'
kbuildsycoca: WARNING: '/usr/share/applications/wine.desktop' specifies undefined mimetype/servicetype 'application/x-winexe'
kbuildsycoca: WARNING: '/usr/share/applications/wine.desktop' specifies undefined mimetype/servicetype 'application/msdos-windows'
kbuildsycoca: WARNING: '/usr/share/applications/wine.desktop' specifies undefined mimetype/servicetype 'application/x-zip-compressed'
kbuildsycoca: WARNING: 'katepart.desktop' specifies undefined mimetype/servicetype 'text/x-fortran'
kbuildsycoca: WARNING: '/usr/share/applications/audacious.desktop' specifies undefined mimetype/servicetype 'audio/mp3'
kbuildsycoca: WARNING: '/usr/share/applications/audacious.desktop' specifies undefined mimetype/servicetype 'audio/x-it'
kbuildsycoca: WARNING: '/usr/share/applications/audacious.desktop' specifies undefined mimetype/servicetype 'audio/x-mpeg'
kbuildsycoca: WARNING: '/usr/share/applications/audacious.desktop' specifies undefined mimetype/servicetype 'audio/x-s3m'
kbuildsycoca: WARNING: '/usr/share/applications/audacious.desktop' specifies undefined mimetype/servicetype 'audio/x-stm'
kbuildsycoca: WARNING: '/usr/share/applications/audacious.desktop' specifies undefined mimetype/servicetype 'audio/x-xm'
kbuildsycoca: WARNING: '/usr/share/applications/audacious.desktop' specifies undefined mimetype/servicetype 'audio/x-vorbis+ogg'
kbuildsycoca: WARNING: 'kcertpart.desktop' specifies undefined mimetype/servicetype 'application/binary-certificate'
Launched ok, pid = 5185

Everything is ok, but I don't like lose control of my system. What can I do with this??

Sorry for my english if is bad.

berbae · 07-11-2007, 11:20 AM

Hi Morroth
Welcome for your first post here.
And congratulations for using this great distro as Arch Linux.
Concerning your question, when the word 'warning' appears in a message, it is not an error but just something that could be better but is not crucial for the good functioning of the system.
So you can ignore those messages.
The 'xset: bad font path element' message is not an error neither.
It just means that you have not installed user fonts, above the system fonts.
I agree the message is not clear, but it's not more serious than that.

You can suppress the 'undefined mimetype/servicetype' messages (but it's not really important) either by creating the mimetype/servicetype in K Menu/ControlCenter/KDE Components/File Associations (I think it's there) or by commenting out the line 'MimeType=' in the desktop files mentioned in the .xsession-errors file.

But you can stay with these messages and others which may happen to appear in that file, if they are not critical (which is generally the case).
Enjoy your Arch Linux experience.

Morroth · 07-11-2007, 12:49 PM

berbare: Thank you very much for your detailed answer