I just did an upgrade, and knetworkmanager seems to have suddenly vanished from the build:
pjh@pjh-laptop:~$ sudo aptitude install knetworkmanager-trinity "knetworkmanager-trinity" exists in the package database, but it is not a real package and no package provides it.
I just did an upgrade, and knetworkmanager seems to have suddenly vanished from the build:
knetwork manager is not available for distributions that use network-manager 0.9 or above due to the fact that critical functionality was removed from the upstream network-manager project.
We are investigating other network management systems for inclusion in TDE as network-manager appears to be a poor choice for TDE at this time.
Tim
Timothy Pearson wrote:
I just did an upgrade, and knetworkmanager seems to have suddenly vanished from the build:
knetwork manager is not available for distributions that use network-manager 0.9 or above due to the fact that critical functionality was removed from the upstream network-manager project.
We are investigating other network management systems for inclusion in TDE as network-manager appears to be a poor choice for TDE at this time.
I suggest using the GTK nm-applet for now. At least on Ubuntu Precise, everything works perfectly when just running nm-applet in a Trinity session. I haven't encountered a single problem yet with it. I do not think it would be wise to try to replace network-manager, because there do not seem to be any alternatives with a comparable amount of features.
Julius
Timothy Pearson wrote:
I just did an upgrade, and knetworkmanager seems to have suddenly vanished from the build:
knetwork manager is not available for distributions that use network-manager 0.9 or above due to the fact that critical functionality was removed from the upstream network-manager project.
We are investigating other network management systems for inclusion in TDE as network-manager appears to be a poor choice for TDE at this time.
I suggest using the GTK nm-applet for now. At least on Ubuntu Precise, everything works perfectly when just running nm-applet in a Trinity session. I haven't encountered a single problem yet with it. I do not think it would be wise to try to replace network-manager, because there do not seem to be any alternatives with a comparable amount of features.
Julius
I am not so sure--nm-applet won't even display it's icon here, and to make matters worse it is a known and ignored upstream bug. The network-manager developers seem to be focusing on Gnome/Unity only; the icon bug also appears on xfce. To top it all off I personally think nm-applet's user interface is rather ugly and difficult to use. :-)
Tim
Timothy Pearson wrote:
Timothy Pearson wrote:
We are investigating other network management systems for inclusion in TDE as network-manager appears to be a poor choice for TDE at this time.
I suggest using the GTK nm-applet for now. At least on Ubuntu Precise, everything works perfectly when just running nm-applet in a Trinity session. I haven't encountered a single problem yet with it. I do not think it would be wise to try to replace network-manager, because there do not seem to be any alternatives with a comparable amount of features.
I am not so sure--nm-applet won't even display it's icon here, and to make matters worse it is a known and ignored upstream bug. The network-manager developers seem to be focusing on Gnome/Unity only; the icon bug also appears on xfce. To top it all off I personally think nm-applet's user interface is rather ugly and difficult to use. :-)
Which version of nm-applet is that? For me, with Ubuntu Precise and the Trinity Nightly builds, the icon always shows up without problems. The version of the package is 0.9.4.1-0ubuntu2. Also notifications from nm-applet work great together with Trinity's notification support!
While its interface could be improved, I don't think it's that bad. I'm not aware of any alternatives that come even close in features or with a better interface. I think at this point it would be easier to cooperate with the Network Manager people to solve small issues that are there than to look for an alternative.
Now that the NM configuration is actually applied at a system-wide level (you do not loose your connection by logging off anymore), the biggest problem I had with NM is completely gone.
Julius
On Friday 20 July 2012 14:58:40 Julius Schwartzenberg wrote:
While its interface could be improved, I don't think it's that bad. I'm not aware of any alternatives that come even close in features or with a better interface. I think at this point it would be easier to cooperate with the Network Manager people to solve small issues that are there than to look for an alternative.
Many of us already use wicd. In fact, one of teh first things I do when I have instralled a system is purge NM and install wicd.
Lisi
On 20 July 2012 10:11, Lisi lisi.reisz@gmail.com wrote:
On Friday 20 July 2012 14:58:40 Julius Schwartzenberg wrote:
While its interface could be improved, I don't think it's that bad. I'm not aware of any alternatives that come even close in features or with a better interface. I think at this point it would be easier to cooperate with the Network Manager people to solve small issues that are there than to look for an alternative.
Many of us already use wicd. In fact, one of teh first things I do when I have instralled a system is purge NM and install wicd.
Lisi
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
I was thinking about creating an trinty wicd applet. Unfortunately the current wicd applets are gtk or for kde4. Also they are written in python which is rather bloated.
Calvin
On Friday 20 July 2012 15:11:05 Calvin Morrison wrote:
I was thinking about creating an trinty wicd applet. Unfortunately the current wicd applets are gtk or for kde4. Also they are written in python which is rather bloated.
Oh. Sorry. :-( They say that ignorance is bliss, but I remain unconvinced.
Lisi
Lisi wrote:
On Friday 20 July 2012 14:58:40 Julius Schwartzenberg wrote:
While its interface could be improved, I don't think it's that bad. I'm not aware of any alternatives that come even close in features or with a better interface. I think at this point it would be easier to cooperate with the Network Manager people to solve small issues that are there than to look for an alternative.
Many of us already use wicd. In fact, one of teh first things I do when I have instralled a system is purge NM and install wicd.
Yes, wicd works very good but there are two big problems with it.
1. People who are not aware of what exactly a supplicant is will not easily set it up. It's configuration, while very powerful, is not really user friendly.
2. It only supports wired and wireless ethernet. This probably works for most cases, but Network Manager offers significantly more which will probably more and more important in the future.
I have used wicd myself as well for a long time, when NM didn't work for me, but nowadays it seems the problems I had with NM have mostly been solved.
Julius
On Friday 20 July 2012 15:29:53 Julius Schwartzenberg wrote:
I have used wicd myself as well for a long time, when NM didn't work for me, but nowadays it seems the problems I had with NM have mostly been solved.
I must admit that it is some time since I tried it. Network Mangler seemed a good nick-name at the time. And I rarely use distros that come with NM.
So I am prepeared to accept that it has changed for the better!
Lisi
-
Calvin Morrison -
Julius Schwartzenberg -
Lisi -
Patricia J. Hawkins -
Timothy Pearson