On Friday, December 10, 2010 23:01:01 sujith h wrote: > After this the application is launched properly. May I know the reason, why > it takes little long time to launch the appliaction > in my system.
There is a DBus call that is being made somewhere which is not being replied to (possibly due to security restrictions on the D-Bus?). Eventually the call times out, sending a "no reply" back to the process which made the call, which then tries to resume starting up. To find out what the call is you'll likely have to use gdb (to attach to the frozen process) and some code inspection in order to find the call that is taking awhile. The process I'd try first is ksmserver. I recently had an issue like this, and it was due to a call out to ConsoleKit even though KDM was not running. Once I started a session from KDM I didn't receive any freezes. You might also be able to run dbus-launch for the system bus at a high debugging level, but I'm not sure whether it actually lists calls in that situation. Regards, - Michael Pyne
signature.asc
Description: This is a digitally signed message part.
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
