[Kde-hardware-devel] Review Request: Adds tab with Mobile Broadband info (depends on ModemManager)

[Lamarque Vieira Souza]

Em Quarta-feira 19 Maio 2010, Lamarque Vieira Souza escreveu:
> Em Quarta-feira 19 Maio 2010, Sebastian Kügler escreveu:
> > Hey,
> > 
> > > > I've just committed a change to not install knm's autostart file by
> > > > default, but load the kded module instead, by the way. So by default,
> > > > you get the Plasmoid now. The default Plasma layout will now also
> > > > enable the NM Plasmoid in the notification area, this change went
> > > > into trunk last weekend.
> > > 	
> > > 	Not working here. I have just ckecked out and compiled
> > > 
> > > kdereview/networkmanagement and it does not load the module
> > > automatically. I added a .desktop file in ~/.config/autostart to make
> > > it load at login.
> > 
> > Did you run kbuildsycoca4? IIRC, itc cache needs refreshing for changes
> > in those .desktop files to work.
> 
> 	I will try.

	Did not work. I logged out, moved my .desktop from ~/.config/autostart, 
run kbuildsycoca4 --noincremental and still no go.
 
> > > 	The disable button works as expected if the connection is *not* set 
to
> > > 
> > > auto-connect. If it is set to auto-connect clicking on disable makes
> > > the connection reconnect, which with my MD300 modem means the
> > > connection will always fail because of the cdc_ether problem I
> > > described above. With wireless clicking on disable makes the
> > > connection reconnects, but I would like it to just disable the
> > > connection instead of reconnect.
> > 
> > Right ... I haven't found a way to tell a connection that has the
> > automatic bit set that it should disconnect and *not* reconnect.
> > Something to figure out.
> 
> 	I will take a look at this.

	NetworkManager-0.8 has a 
"org.freedesktop.NetworkManager.Device.Disconnect" method to disconnect one 
device and prevent it from autoconnecting 
(http://projects.gnome.org/NetworkManager/developers/spec-08.html). Solid only 
supports NetworkManager-0.7, we need to upgrade solid's NM implementation to 
0.8 version to make use of this feature. This feature is per device, not 
connection, in wireless case all networks would be prevented from 
autoconnection, not only the clicked one.
 
> > > 	I think there is no button to launch the notification configuration 
in
> > > 
> > > the plasmoid's config dialog, only for "connections" and "other"
> > > configurations. I far as I know the notification infra-structure is
> > > shared between the plasmoid and knm, right? I have already setup the
> > > notifications in system settings to work with knm, so they should work
> > > with plasmoid too, right? It sems kded module does not use
> > > ./libs/service/notificationmanager.*
> > 
> > Haven't looked into this, that's more Will's domain.
> 
> 	This is one thing I would like have implemented. I can try to make it
> work. Some weeks ago Will was moving to a new appartment, since then I have
> not heard of him.
> 
> > > 	Two other problems I have just found: 1. the plasmoid layout gets
> > > 	messed
> > > 
> > > up if I go to one of the interface detail windows because the traffic
> > > monitor is too big for the plasmoid window. 2. The "back" button in
> > > interface details does not work anymore, I can click on it but it does
> > > nothing.
> > 
> > That should not happen, can you send me a screenshot, so I understand the
> > problem better?

	Here it is http://www.kde-
mg.org/sites/default/files/lamarque/screenshot11.jpg
 
-- 
Lamarque V. Souza
http://www.geographicguide.com/brazil.htm
Linux User #57137 - http://counter.li.org/
http://www.kde-mg.org