|Summary:||knetworkmanager doesn't compile with networkmanager-0.7.0|
|Product:||Gentoo Linux||Reporter:||Jens Weibler <gentoo-bugzilla>|
|Component:||[OLD] KDE||Assignee:||Robert Buchholz (RETIRED) <rbu>|
|Severity:||normal||CC:||c.nothhelfer, dagger, hanno, Jens.Rutschmann, mappam0, me, nasvit-chmo, novachok, olemarkus, oracleguy01, piorekf, r.snajdr, r_meier, spatz, StormByte, treecleaner|
|Package list:||Runtime testing required:||---|
|Bug Depends on:|
|Bug Blocks:||197488, 217209, 255864, 268732|
|Attachments:||emerge knetworkmanager log|
Description Jens Weibler 2009-01-04 22:04:18 UTC
knetworkmanager doesn't compile with the latest networkmanager (0.7.0). Many include-files aren't delivered anymore with networkmanager: NetworkManager/cipher.h NetworkManager/cipher-w* ... Reproducible: Always Steps to Reproduce:
Comment 1 Jens Weibler 2009-01-04 22:05:17 UTC
Created attachment 177413 [details] emerge knetworkmanager log
Comment 2 Robert Buchholz (RETIRED) 2009-01-07 13:07:33 UTC
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.
Comment 3 Tomáš Chvátal (RETIRED) 2009-01-07 13:18:57 UTC
afaik they are working on nm-applet for plasma in kde4. so i guess you can harddep on older version for kde3 :]
Comment 4 Robert Piasek (RETIRED) 2009-01-08 01:20:10 UTC
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).
Comment 5 Tom Barbette 2009-01-23 15:56:01 UTC
*** Bug 255373 has been marked as a duplicate of this bug. ***
Comment 6 Kevin 2009-01-23 17:42:26 UTC
(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?
Comment 7 Martin Gysel (bearsh) 2009-04-15 07:59:50 UTC
(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
Comment 8 Martin Gysel (bearsh) 2009-04-15 08:04:50 UTC
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.  http://bitbucket.org/bearsh/bearshoverlay/src/tip/kde-misc/knetworkmanager/  http://patch-tracking.debian.net/package/knetworkmanager/1:0.7~~svn941706-1
Comment 9 Piotr 2009-04-25 20:49:12 UTC
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?
Comment 10 Piotr 2009-05-05 20:15:28 UTC
Does any one remember this bug? Will there ever be a new knetworkmanager in portage? At least in testing branch?
Comment 11 Alexandr Novachok 2009-05-11 11:00:41 UTC
I'm waiting for resolution too
Comment 12 Robert Buchholz (RETIRED) 2009-05-12 22:05:26 UTC
*** Bug 268499 has been marked as a duplicate of this bug. ***
Comment 13 Robert Piasek (RETIRED) 2009-05-27 15:18:08 UTC
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. Rob
Comment 14 Piotr 2009-07-25 08:48:18 UTC
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: <policy group="plugdev"> <allow own="org.freedesktop.NetworkManagerUserSettings"/> <allow send_destination="org.freedesktop.NetworkManagerUserSettings" send_interface="org.freedesktop.NetworkManagerSettings"/> <allow send_destination="org.freedesktop.NetworkManagerUserSettings" send_interface="org.freedesktop.NetworkManagerSettings.Connection"/> <!-- Only root can get secrets --> <deny send_destination="org.freedesktop.NetworkManagerUserSettings" send_interface="org.freedesktop.NetworkManagerSettings.Connection.Secrets"/> </policy>
Comment 15 Robert Buchholz (RETIRED) 2009-10-21 09:26:30 UTC
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)?
Comment 16 Luca Santarelli 2009-10-24 15:48:33 UTC
(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.
Comment 17 Samuli Suominen (RETIRED) 2009-11-12 13:02:43 UTC
There's a new knetworkmanager in kde-testing, planned for KDE 4.4. Meanwhile, use wicd.