KNetworkManager broken by default due to conflict between KDED based module and monolithic client

[Sebastian Kügler]

On Sunday 13 December 2009 12:50:02 Ben Cooksley wrote:
> On Mon, Dec 7, 2009 at 6:11 AM, Will Stephenson <wstephenson at kde.org> wrote:
> > On Sunday 06 December 2009 09:25:21 Ben Cooksley wrote:
> >> Hi Will,
> >>
> >> Any idea when the changes were introduced that made the KDE Daemon
> >> module claim the dbus interface
> >> "org.freedesktop.NetworkManagerUserSettings" which causes the
> >> monolithic client to fail to start up? I encountered this when
> >> starting my system up after my usual SVN update & build just now, and
> >> had to unload the module to get it to start ( and thus be able to
> >> connect to my wireless network )
> >
> > From "svn log
> > svn+ssh://wstephens@svn.kde.org/home/kde/trunk/kdereview/networkmanagemen
> >t/kded/networkmanagement.desktop":
> >
> > r1057286 | sebas | 2009-12-01 23:06:18 +0100 (Tue, 01 Dec 2009) | 1 line
> >
> > automatically load our kded module
> >
> > --
> >
> > I'm not sure if this is the right thing to do OOTB, but nothing better
> > than the 'plasmoid tells kded to load the module on load and
> > knetworkmanager tells kded to unload the module on startup' we used in
> > the last iteration occurs to me right now, and I didn't like that much
> > then.  Any ideas?  Exclusively choose one or the other to build and
> > install at cmake time? (this won't fly for distros, so don't go there
> > :)).
> 
> Perhaps, since the kded module was supposed to be shared,
> knetworkmanager could check if it is loaded and use it instead of its
> own internal functionality?
> 
> However, there does not appear to have been any movement on this front :(
> 
> As the breakage still exists, I intend to revert commit 1057286 in 24
> hours to restore the monolithic client to a functional status, as
> using hacks is better than being completely and utterly broken.

Go for it, as knetworkmanager is more stable than the plasmoid, it should be used and 
work. In the end, they shouldn't run together, but this should probably solved on 
package level (conflicts, or somesuch). We'll have to discuss how to go about this, 
but having knetworkmanager use the kded module is not quite so trivial.
-- 
sebas

http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 489 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/kde-networkmanager/attachments/20091213/10e7b7e1/attachment.sig