Jan Grulich

Plasma-nm release

I just want to inform you (those who are still running KDE 4) that we released a new version of your favorite network applet. This new release brings to you many bug fixes and should make your life easier. We really recommend to update to the new version as we, not intentionally, introduced some new issues in the previous version. Together with the new release of plasma-nm we also released our libnm-qt library which is also needed if you want to have fixes from plasma-nm properly working.

Summary of fixed issues:
bz#339652 – added missing IPv6 support for OpenVPN connections
bz#333752 – we moved code for checking your current download/upload to QML code and now it just checking for updates only when the applet is opened
bz#329837 – during import of VPN connections we copied your certificates automatically into your home directory, now we are asking whether you want to copy them or keep the path as it is
bz#340306 – fixed initialization of current download/upload speed for mobile broadband connections
bz#338513, bz#338697, bz#339223 – many fixes in secret agent (KWallet) initialization, also added migration for your secrets from plain text files, we dropped their support in the previous version, and store them into KWallet or directly into NetworkManager (if KWallet is not enabled)

You can find new tarballs in usual location, which is [1] for plasma-nm and [2] for libnm-qt.

[1] – http://download.kde.org/stable/plasma-nm/plasma-nm-
[2] – http://download.kde.org/unstable/networkmanager-qt/

11 thoughts on “Plasma-nm release

  1. Plasma-NM depends on libnm-qt, right?
    Stupid question probably but how can something (Plasma-NM in this case) be stable when it depends on something unstable (libnm-qt)?
    I could imagine the other way around but this seems strange.

    1. libnm-qt is also stable, it’s just in wrong directory. I don’t know why, you would have to ask Lamarque Souza.

  2. What happens when multiple connections are active? If you use kvm or VirtualBox they create their own bridged connection which activates on their own, so often times there are two or three connections active – for example, my actual internet connection and virbr0. I somehow feel like these multiple active connections slow down or interfere in my internet connectivity.

    What do you think about changing icons when multiple connections are active? Letting users know what kind of connected they are actually connected to – wifi, virtual, etc.

    1. This is all managed by NetworkManager itself and we do not control which connections are created and activated automatically.

      Having various icons for this case would be complicated. You would need to create icons for all possible cases/combinations. You can see all active connections in tooltip when you have mouse over the plasma-nm icon is systray.

  3. I would like to suggest some enhancements for your consideration.

    1. I sometimes run with several wireless NICs in the computer, and there are several APs in my neighborhood. As a result, the display of possible connections gets quite long. Would it be possible to be able to select the possibilities by interface name as was done in a previous applet?

    2. At present, there is a separate entry in the Connection Editor for each AP and device name combination. Why? The “secret” depends only on the AP. The present behavior makes the table have an excessive length, and it is necessary to re-enter the encryption secret for every new NIC.

    3. Would it be possible to add a scrollbar to the available connections screen for those of us that use laptops rather than tablets? At present, my list has 26 entries, and it takes 3 different pulls to drag from top to bottom. A scroll bar would be proportional, and a single drag could cover the entire list.

    1. 1) Probably not in the applet as it’s quite small and there is no much space for new options, but I would like to have something like that in KCM which we are planning for Plasma 5.

      2) This is not possible, because each connection has it’s own UUID and it doesn’t depend on AP or on device. Well, in someway it could be possible, but I don’t think it is worth doing it that way. Anyway, NM is asking for a password for a given connection, not given AP and device and also one connection could work for more than one AP and device.

      3) Unfortunately not in KDE 4 version as this component is broken. We already have a scrollbar in Plasma 5 version.

      1. Thanks for answering. I am still not sure why the connection UUID is used rather than the AP/SSID, but I will take your word that it is necessary. I look forward to the Plasma 5 release.

  4. What dependency does it have, strongswan or openswan? It seems that in the case of strongswan (v5.2.1) the script /usr/sbin/ipsec is called with nonexistant arguments:

    /usr/sbin/ipsec: line 25: uname: command not found
    /usr/sbin/ipsec: line 27: uname: command not found
    /usr/sbin/ipsec: unknown IPsec command `setup’ (`ipsec –help’ for list)
    /usr/sbin/ipsec: line 25: uname: command not found
    /usr/sbin/ipsec: line 27: uname: command not found
    /usr/sbin/ipsec: unknown IPsec command `whack’ (`ipsec –help’ for list)

    Not mentioning some strange fault in PATH.

  5. Pretty section of content. I just stumbled upon your site and in accession capital to assert that I get in fact enjoyed account your blog posts.

    Any way I’ll be subscribing to your augment and even I
    achievement you access consistently rapidly.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Scroll To Top