knetworkmanager doesn't compile with the latest networkmanager (0.7.0).
Many include-files aren't delivered anymore with networkmanager:
Steps to Reproduce:
Created attachment 177413 [details]
emerge knetworkmanager log
Known issue, that's why it is under package.mask (among other reasons). KNM upstream is working on 0.7 support, but is not there yet.
afaik they are working on nm-applet for plasma in kde4. so i guess you can harddep on older version for kde3 :]
plasma applet for kde4 works ok already (they even commited VPN plugins recently), but got kde3 knetworkmanager is still under way.
On the other hand we could bump the snapshot for kde3. I think recent trunk compiles fine against 0.7.0 (last time I checked it did).
*** Bug 255373 has been marked as a duplicate of this bug. ***
(In reply to comment #4)
> plasma applet for kde4 works ok already (they even commited VPN plugins
> recently), but got kde3 knetworkmanager is still under way.
> On the other hand we could bump the snapshot for kde3. I think recent trunk
> compiles fine against 0.7.0 (last time I checked it did).
On the KNM page they list the svn sources for KNM 0.7, is that the plasma applet you are talking about or is that the frontend for KDE3? If it is, has anyone tried it yet?
(In reply to comment #6)
> On the KNM page they list the svn sources for KNM 0.7, is that the plasma
> applet you are talking about or is that the frontend for KDE3? If it is, has
> anyone tried it yet?
KNM 0.7 for kde3 can be found here: http://websvn.kde.org/branches/work/knetworkmanager
in my overlay, there's a recent version of KNM (20090414) which seems to work with 0.7.1-rc3 from rbu's overlay. I had to apply some patches from debian  to get the wireless part working. Whould be nice to see a recent version like this in portage soon.
networkmanager-7.1 is in ~x86. How about knetworkmanager? Due to the lack of relevant knetworkmanager I had to mask new networkamanger.
How about some test release? Even masked?
Does any one remember this bug?
Will there ever be a new knetworkmanager in portage? At least in testing branch?
I'm waiting for resolution too
*** Bug 268499 has been marked as a duplicate of this bug. ***
There is an ebuild in rbu's overlay for knetworkmanager.
It's reported to work, although VPNC support seems broken. If you want - please give it a try.
With dbus-1.2.12 knetworkmanager from rbu's overlay doesn't work. To solve it you must add to /etc/dbus-1/system.d/knetworkmanager.conf this section:
<!-- Only root can get secrets -->
I just noticed treecleaners taking over this bug, and I do not object to knetworkmanager's removal. My only question is (to dagger/kde team) whether the kde4 NM plasmoid is up and working fine? Can we add an upgrade path to the masking note (what steps need to be taken)?
(In reply to comment #15)
> I just noticed treecleaners taking over this bug, and I do not object to
> knetworkmanager's removal.
Neither do I, provided that you keep your overlay active! :)
As a side note (let me know if this is a "hijack" of the bug) the SRC_URI for dev-libs/dbus-qt3-0.9 went down. I talked to Kevin Krammer and he uploaded the latest code he could find on his computer, using the same version number but obviously with a different MD5 sum of the gzip file. Could you "bump" a -r1 with a different manifest/digest in your overlay?
I forced a manifest on the new file, went with the update and now I'm writing from a working knetworkmanager-ed laptop. :)
Note: I had to add the code in comment #4.
There's a new knetworkmanager in kde-testing, planned for KDE 4.4. Meanwhile, use wicd.