Hi guys! I can't get that kde 4.8 works well. Sometimes it starts and sometimes not; It hangs on the last icon on the splash screen, that belongs to k menu.

Here are the system logs

http://pastebin.com/yERaj65X

Any help will be wellcome

Regards.

are you starting KDE with by restoring an previous session or starting an empty one?

if you create a new user does it experience this problem?

please note: when you have such a large amount of logs to display it would more appropriate to use pastebin.com and just place a link to the the text

Hello.

I followed your suggestions.

1) Was not problem of the previous version.

2) When I created a new user, I did not experience the problem until use kdm to change the start atributtes of the new sesion (for automatic login of user).

¿Could be an error of kdm? ¿corrupts in some circunstancies the kde start process?

I solved it simply doing a copy of .kde and restoring it after experience of hang after change kdm attributes

maybe create new post with subject something like "KDE session hangs/freezes when auto login is enabled at KDE icon on the KDE splash screen", make sure you note in the post that it did not occur until you updated to 4.8

could you try disabling desktop effects at start up in systemsettings -> desktop effects -> general

Have you verified that all necessary or optional services, including the System D-Bus instance, UDisks, UPower, UDev, NetworkManager, ModemManager, Bluetoothd, Polkit, CUPS and ConsoleKit are all operating when KDM attempts to perform the login?

UDisks and UPower should be autolaunched by the System D-Bus instance when KDE first queries them. Bluetoothd is only required if your system has Bluetooth hardware and you have Bluedevil installed. CUPS is only needed if your system uses a Printer. NetworkManager and ModemManager are only required if you use KDE Network Management.

UDisks, UPower, UDev, Polkit and ConsoleKit and all heavily recommended/required dependencies.

If you have any of these services on your system, and their startup is delayed - or they are not responsive for part of their startup, then this could explain the failure to start, or the slow nature of the startup.

Also, it may be worth checking that all file systems - especially temporary ones which may be created over /tmp or /var/tmp are mounted prior to KDE/KDM startup commencing.