commit 302b8b16f15aada683d64602b923cc54e11f2816

Lamarque Vieira Souza lamarque at gmail.com
Mon May 23 02:00:47 CEST 2011


commit 302b8b16f15aada683d64602b923cc54e11f2816
Author: Ilia Kats <ilia-kats at gmx.net>
Date:   Mon May 23 01:12:10 2011 +0200

    Code cleanup:
    
    remove all *persistence, merge nmdbussettingsservice into
    nmdbussettingsconnectionprovider and remove nmdbussettingsservice.
    
    This fixes the issue that connections could not be activated from
    Plasma NM. WARNING: if kded is started after plasma/restarted while
    plasma is running, plasma will crash when activating a connection.
    kded has to be started before plasma.



	Hi Ilia. The commit above is not acceptable, we should add a restriction 
that we cannot control. That situation is going to happen and users are going 
to fill bugs.kde.org with complaints.

	Why kded has to be started first?

-- 
Lamarque V. Souza
http://www.geographicguide.com/brazil.htm
Linux User #57137 - http://counter.li.org/
http://planetkde.org/pt-br
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/kde-networkmanager/attachments/20110522/bfb570ec/attachment.htm 


More information about the kde-networkmanager mailing list