[aKregator-devel] [Bug 169304] akregator does not start immediately when using the --nofork command line option

[Teemu R. <tp...@d5...>]

http://bugs.kde.org/show_bug.cgi?id=169304


Teemu Rytilahti tpr d5k net changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tp...@d5...




--- Comment #1 from Teemu Rytilahti <tpr d5k net>  2008-08-19 02:29:20 ---
Those delays happen when Application::newInstance() tries to set-up connection
to the D-Bus interface for loading up the feedlist and stuff. Tried to see
around what could cause it, but didn't find any apparent reason for it.
According to QDbusConnection's isConnected() we at least have a connection..

Calling qdbus org.kde.akregator causes qdbus to freeze also after displaying
only '/'. Tried to move loadPart() call before creation of the QDBusInterface
for it, but that didn't help. QDBusConnection::sessionBus().registerObject() in
Part::Part() for that interface returns true though.

Anyways, for me this sounds more like a bug in KUniqueApplication than in
Akregator. What do you think Frank?


-- 
Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.