|
||||||
| Forums FAQ | Members List | Search | Today's Posts | Mark Forums Read |
| ARCHIVES - OpenSUSE Beta Questions specific to OpenSUSE Linux Beta releases
(Questions that apply to both beta and release versions should be posted in the appropriate SUSE Help forums) |
|
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
I am running RC1_x64_KDE4 on my laptop and everything is working okay so far apart from some minor issues, but what I find really annoying is that I have no less then 3 (!) Knetworkmanger applets running in the tray.
1) a green globe 2) a pinguinwith a red cross for the unused wired conection 3) an antenna for my wireless connection why are these not combined into one networking applet like I am used to, this causes so much clutter in the huge KDE panel. With my 4 virtual desktops, fusion icon, volume, etc. the space for active applications is virtually non-existent. stefan |
|
|||
|
same annoying problem here, there was a bug report but it was closed, This is something that will be fixed in the KDE4 version (one we run now is KDE3)
|
|
|||
|
Quote:
|
|
|||
|
One advantage of the new knetworkmanager in 11.0 is that it allows multiple connections to be active simultaneously (whereas the previous version would prefer ethernet over wireless). The drawback is that, right now, it displays an icon indicator for each interface detected, whether active or not. I don't think there's a way to disable that functionality.
The globe thing is, IMHO, pointless. It fades to gray on the lack of an active connection, or turns green with an active connection. But it's pretty redundant since the interface icons display connectivity anyways. Unfortunately, with the release of the 0.7 series of networkmanager, and the release timing for openSUSE 11, they didn't have as much time as they'd like to produce a well integrated version of knetworkmanager. The changes with 0.7 were significant enough that the old version couldn't simply be ported. And of course, since networkmanager is maintained by Red Hat, they only ensured that the gnome client was developed alongside and ready for release at the same time. The KDE devs had to play catchup. Which is a shame, because it means that the Fedora 9 KDE users have to use the gnome applet by default, instead of having access to knetworkmanager. So the alternative would have been to stick with the previous version of networkmanager, which would have restricted acccess to the newer features, or to use the gnome client as a default app for networkmanager in KDE, which would have been icky. Though that's still an option if you'd prefer to try that instead of the KDE client. By the time KDE 4.2 rolls out, networkmanager support will be integrated into KDE so a separate client app will be redundant. Until then, this is what we have... Though I'm sure updated versions will be made available via the build-service as they are released. Hope this helps... Cheers, KV |
|
|||
|
The most annoying thing for me is that it lacks the vpn functionality the previous version had. It worked a lot better for me than kvpnc did and I didn't need yet another program running.
|
|
|||
|
Quote:
|
|
|||
|
Quote:
Cheers, KV |
|
|||
|
Factory has commits fixing it in the commit mail list
|
|
|||
|
hi all,
am i only one who having this problem - my connections wont reconnect automatically. every time i reboot computer i have to go to networkmanager and with right click select network from the "available wireless connections" list. is there any way to make it connect automatically? thnx |
|
|||
|
Quote:
|
|
| Bookmarks |
| Thread Tools | |
| Display Modes | |
|
|