Hi,
we've prepared testing builds of kde-plasma-nm including libnm-qt and libmm-qt libraries in COPR repository [1]. The testing version includes a new design and few bugfixes and it is almost ready for stable release, we are just polishing its design. If you want to try it, just add the COPR repository and run update of kde-plasma-nm together with libnm-qt and libmm-qt and you also need to update NetworkManager from updates-testing repository (currently there is NetworkManager-0.9.9.0-29.git20140131.fc20).
Positive or negative feedback is welcomed. Thanks.
[1] http://copr.fedoraproject.org/coprs/jgrulich/plasma-nm/
Cheers, Jan
On 02/10/2014 07:40 AM, Jan Grulich wrote:
Hi,
we've prepared testing builds of kde-plasma-nm including libnm-qt and libmm-qt libraries in COPR repository [1]. The testing version includes a new design and few bugfixes and it is almost ready for stable release, we are just polishing its design. If you want to try it, just add the COPR repository and run update of kde-plasma-nm together with libnm-qt and libmm-qt and you also need to update NetworkManager from updates-testing repository (currently there is NetworkManager-0.9.9.0-29.git20140131.fc20).
Positive or negative feedback is welcomed. Thanks.
[1] http://copr.fedoraproject.org/coprs/jgrulich/plasma-nm/
Cheers, Jan
In general, looks much better, thanks! Couple comments:
- I have some virbr0 interfaces:
3: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default link/ether 52:54:00:6c:03:49 brd ff:ff:ff:ff:ff:ff inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0 valid_lft forever preferred_lft forever 4: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr0 state DOWN group default qlen 500 link/ether 52:54:00:6c:03:49 brd ff:ff:ff:ff:ff:ff
- in the widget virbr0 shows up in the available connections as "Connecting" and has a spinner going. I'm not sure if this was present under the old version or not - but it seems not correct to me.
- I can't decide if having to click on the Connect/Disconnect button is a pain or not - I'd be tempted to be able to click anywhere on the connection to do that.
Dne Po 10. února 2014 09:51, Orion Poplawski napsal(a):
On 02/10/2014 07:40 AM, Jan Grulich wrote:
Hi,
we've prepared testing builds of kde-plasma-nm including libnm-qt and libmm-qt libraries in COPR repository [1]. The testing version includes a new design and few bugfixes and it is almost ready for stable release, we are just polishing its design. If you want to try it, just add the COPR repository and run update of kde-plasma-nm together with libnm-qt and libmm-qt and you also need to update NetworkManager from updates-testing repository (currently there is NetworkManager-0.9.9.0-29.git20140131.fc20).
Positive or negative feedback is welcomed. Thanks.
[1] http://copr.fedoraproject.org/coprs/jgrulich/plasma-nm/
Cheers, Jan
In general, looks much better, thanks! Couple comments:
- I have some virbr0 interfaces:
3: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default link/ether 52:54:00:6c:03:49 brd ff:ff:ff:ff:ff:ff inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0 valid_lft forever preferred_lft forever 4: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr0 state DOWN group default qlen 500 link/ether 52:54:00:6c:03:49 brd ff:ff:ff:ff:ff:ff
- in the widget virbr0 shows up in the available connections as "Connecting"
and has a spinner going. I'm not sure if this was present under the old version or not - but it seems not correct to me.
According to google, virbr device (virtual bridge) comes from libvirt and it's possible that NetworkManager is trying to activate them, but without success, because it's not probably properly configured, so I would suggest to disable autoconnect.
- I can't decide if having to click on the Connect/Disconnect button is a pain
or not - I'd be tempted to be able to click anywhere on the connection to do that.
I would say that compared to the previous version it's a relief :)
Cheers, Jan
On 02/10/2014 10:29 AM, Jan Grulich wrote:
Dne Po 10. února 2014 09:51, Orion Poplawski napsal(a):
On 02/10/2014 07:40 AM, Jan Grulich wrote:
Hi,
we've prepared testing builds of kde-plasma-nm including libnm-qt and libmm-qt libraries in COPR repository [1]. The testing version includes a new design and few bugfixes and it is almost ready for stable release, we are just polishing its design. If you want to try it, just add the COPR repository and run update of kde-plasma-nm together with libnm-qt and libmm-qt and you also need to update NetworkManager from updates-testing repository (currently there is NetworkManager-0.9.9.0-29.git20140131.fc20).
Positive or negative feedback is welcomed. Thanks.
[1] http://copr.fedoraproject.org/coprs/jgrulich/plasma-nm/
Cheers, Jan
In general, looks much better, thanks! Couple comments:
- I have some virbr0 interfaces:
3: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default link/ether 52:54:00:6c:03:49 brd ff:ff:ff:ff:ff:ff inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0 valid_lft forever preferred_lft forever 4: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr0 state DOWN group default qlen 500 link/ether 52:54:00:6c:03:49 brd ff:ff:ff:ff:ff:ff
- in the widget virbr0 shows up in the available connections as "Connecting"
and has a spinner going. I'm not sure if this was present under the old version or not - but it seems not correct to me.
According to google, virbr device (virtual bridge) comes from libvirt and it's possible that NetworkManager is trying to activate them, but without success, because it's not probably properly configured, so I would suggest to disable autoconnect.
It's working fine. I'm more thinking that kde shouldn't even show it - perhaps not show any bridge connections? But perhaps there is some other bug that:
# nmcli c show virbr0 .... GENERAL.STATE: activating
which is probably why the kde widget shows the spinner.
- I can't decide if having to click on the Connect/Disconnect button is a pain
or not - I'd be tempted to be able to click anywhere on the connection to do that.
I would say that compared to the previous version it's a relief :)
Oh, it's definitely better! But it still seems limiting that you have to click on a smallish button to connect rather than just anywhere on the connection box.
On 02/10/2014 01:43 PM, Orion Poplawski wrote:
On 02/10/2014 10:29 AM, Jan Grulich wrote:
Dne Po 10. února 2014 09:51, Orion Poplawski napsal(a):
- I have some virbr0 interfaces:
3: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default link/ether 52:54:00:6c:03:49 brd ff:ff:ff:ff:ff:ff inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0 valid_lft forever preferred_lft forever 4: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr0 state DOWN group default qlen 500 link/ether 52:54:00:6c:03:49 brd ff:ff:ff:ff:ff:ff
- in the widget virbr0 shows up in the available connections as "Connecting"
and has a spinner going. I'm not sure if this was present under the old version or not - but it seems not correct to me.
According to google, virbr device (virtual bridge) comes from libvirt and it's possible that NetworkManager is trying to activate them, but without success, because it's not probably properly configured, so I would suggest to disable autoconnect.
It's working fine. I'm more thinking that kde shouldn't even show it - perhaps not show any bridge connections? But perhaps there is some other bug that:
# nmcli c show virbr0 .... GENERAL.STATE: activating
which is probably why the kde widget shows the spinner.
This turns out to be a NetworkManager issue. Downgrading from NetworkManager-0.9.9.0-29.git20140131.fc20 to NetworkManager-0.9.9.0-28.git20131003.fc20 remove virbr0 from the list of active connections.
Dne Po 10. února 2014 13:55, Orion Poplawski napsal(a):
On 02/10/2014 01:43 PM, Orion Poplawski wrote:
On 02/10/2014 10:29 AM, Jan Grulich wrote:
Dne Po 10. února 2014 09:51, Orion Poplawski napsal(a):
- I have some virbr0 interfaces:
3: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default link/ether 52:54:00:6c:03:49 brd ff:ff:ff:ff:ff:ff inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0 valid_lft forever preferred_lft forever 4: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr0 state DOWN group default qlen 500 link/ether 52:54:00:6c:03:49 brd ff:ff:ff:ff:ff:ff
- in the widget virbr0 shows up in the available connections as "Connecting"
and has a spinner going. I'm not sure if this was present under the old version or not - but it seems not correct to me.
According to google, virbr device (virtual bridge) comes from libvirt and it's possible that NetworkManager is trying to activate them, but without success, because it's not probably properly configured, so I would suggest to disable autoconnect.
It's working fine. I'm more thinking that kde shouldn't even show it - perhaps not show any bridge connections? But perhaps there is some other bug that:
# nmcli c show virbr0 .... GENERAL.STATE: activating
which is probably why the kde widget shows the spinner.
This turns out to be a NetworkManager issue. Downgrading from NetworkManager-0.9.9.0-29.git20140131.fc20 to NetworkManager-0.9.9.0-28.git20131003.fc20 remove virbr0 from the list of active connections.
That's possible, but I'm not sure whether this version of NetworkManager will work correctly with the latest libnm-qt, because we use some stuff from the latest version.
Cheers, Jan
On Monday 10 February 2014 15:40:02 Jan Grulich wrote:
Hi,
we've prepared testing builds of kde-plasma-nm including libnm-qt and libmm-qt libraries in COPR repository [1]. The testing version includes a new design and few bugfixes and it is almost ready for stable release, we are just polishing its design. If you want to try it, just add the COPR repository and run update of kde-plasma-nm together with libnm-qt and libmm-qt and you also need to update NetworkManager from updates-testing repository (currently there is NetworkManager-0.9.9.0-29.git20140131.fc20).
Positive or negative feedback is welcomed. Thanks.
[1] http://copr.fedoraproject.org/coprs/jgrulich/plasma-nm/
Cheers, Jan
It works but the connection icons are/look stretched as the picture attached shows. FWIW the right side of the figure has been cropped by the snap shot application but it is present here, so not a problem.
On 02/11/2014 11:06 AM, José Matos wrote:
On Monday 10 February 2014 15:40:02 Jan Grulich wrote:
Hi,
we've prepared testing builds of kde-plasma-nm including libnm-qt and libmm-qt libraries in COPR repository [1]. The testing version includes a new design and few bugfixes and it is almost ready for stable release, we are just polishing its design. If you want to try it, just add the COPR repository and run update of kde-plasma-nm together with libnm-qt and libmm-qt and you also need to update NetworkManager from updates-testing repository (currently there is NetworkManager-0.9.9.0-29.git20140131.fc20).
Positive or negative feedback is welcomed. Thanks.
[1] http://copr.fedoraproject.org/coprs/jgrulich/plasma-nm/
Cheers, Jan
It works but the connection icons are/look stretched as the picture attached shows. FWIW the right side of the figure has been cropped by the snap shot application but it is present here, so not a problem.
I see this on one of my systems, but not others. Air for netbooks and Oxygen.
Biggest problem is with the toggles on the top.
Dne Út 11. února 2014 20:45, Orion Poplawski napsal(a):
On 02/11/2014 11:06 AM, José Matos wrote:
On Monday 10 February 2014 15:40:02 Jan Grulich wrote:
Hi,
we've prepared testing builds of kde-plasma-nm including libnm-qt and libmm-qt libraries in COPR repository [1]. The testing version includes a new design and few bugfixes and it is almost ready for stable release, we are just polishing its design. If you want to try it, just add the COPR repository and run update of kde-plasma-nm together with libnm-qt and libmm-qt and you also need to update NetworkManager from updates-testing repository (currently there is NetworkManager-0.9.9.0-29.git20140131.fc20).
Positive or negative feedback is welcomed. Thanks.
[1] http://copr.fedoraproject.org/coprs/jgrulich/plasma-nm/
Cheers, Jan
It works but the connection icons are/look stretched as the picture attached shows. FWIW the right side of the figure has been cropped by the snap shot application but it is present here, so not a problem.
I see this on one of my systems, but not others. Air for netbooks and Oxygen.
Biggest problem is with the toggles on the top.
This happens, because we have new icons, so you have to clear your icon cache in ~/.kde/cache-your-hostname and probably run kbuildsycoca4 --noincremental.
Cheers, Jan
On 02/12/2014 01:39 AM, Jan Grulich wrote:
This happens, because we have new icons, so you have to clear your icon cache in ~/.kde/cache-your-hostname and probably run kbuildsycoca4 --noincremental.
Cheers, Jan
Hmm, I ended up logging out, removing the cache, and logging back in - that finally did it.
One more problem though - the bottom part of the popup window appears to be covered by the bottom panel. When I cursor off of the panel and it auto-hides, the popup is still truncated and you see the window beneath it.
Dne St 12. února 2014 09:55, Orion Poplawski napsal(a):
On 02/12/2014 01:39 AM, Jan Grulich wrote:
This happens, because we have new icons, so you have to clear your icon cache in ~/.kde/cache-your-hostname and probably run kbuildsycoca4 --noincremental.
Cheers, Jan
Hmm, I ended up logging out, removing the cache, and logging back in - that finally did it.
One more problem though - the bottom part of the popup window appears to be covered by the bottom panel. When I cursor off of the panel and it auto-hides, the popup is still truncated and you see the window beneath it.
I forgot that you have to restart plasma-desktop. Can you please send a screenshot of your problem?
Cheers, Jan
Jan Grulich wrote:
This happens, because we have new icons, so you have to clear your icon cache in ~/.kde/cache-your-hostname and probably run kbuildsycoca4 --noincremental.
We had a small discussion about this issue on IRC. What keeps me puzzled is that the icons end up stretched that way even though both the old and the new icons are supposed to be square.
Kevin Kofler
On 02/10/2014 07:40 AM, Jan Grulich wrote:
Hi,
we've prepared testing builds of kde-plasma-nm including libnm-qt and libmm-qt libraries in COPR repository [1]. The testing version includes a new design and few bugfixes and it is almost ready for stable release, we are just polishing its design. If you want to try it, just add the COPR repository and run update of kde-plasma-nm together with libnm-qt and libmm-qt and you also need to update NetworkManager from updates-testing repository (currently there is NetworkManager-0.9.9.0-29.git20140131.fc20).
Positive or negative feedback is welcomed. Thanks.
[1] http://copr.fedoraproject.org/coprs/jgrulich/plasma-nm/
Cheers, Jan
Now on my desktop with:
NetworkManager-0.9.9.0-30.git20131003.fc20.x86_64 kde-plasma-nm-0.9.3.3-2.201402137586912.fc20.x86_64 libnm-qt-0.9.9.0-2.20140213d053b27.fc20.x86_64 libmm-qt-1.2.0-1.20140106gitac3f564.fc20.x86_64
I get a completely blank window except for the control buttons across the top. Does it no longer show "system" connections?
STATE CONNECTIVITY WIFI-HW WIFI WWAN-HW WWAN connected full enabled enabled enabled disabled $ nmcli c NAME UUID TYPE TIMESTAMP-REAL cora-client 62b18ffa-6d34-4b09-970f-8146abe27a9b vpn never
CORA b80647f2-abec-439a-9459-d79cd56c6f86 802-11-wireless never
System eth0 5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03 802-3-ethernet Fri 21 Feb 2014 08:50:35 AM MST $ nmcli c show active NAME UUID DEVICES DEFAULT VPN MASTER-PATH System eth0 5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03 eth0 yes no --
On Friday 21 of February 2014 08:53 Orion Poplawski wrote:
On 02/10/2014 07:40 AM, Jan Grulich wrote:
Hi,
we've prepared testing builds of kde-plasma-nm including libnm-qt and libmm-qt libraries in COPR repository [1]. The testing version includes a new design and few bugfixes and it is almost ready for stable release, we are just polishing its design. If you want to try it, just add the COPR repository and run update of kde-plasma-nm together with libnm-qt and libmm-qt and you also need to update NetworkManager from updates-testing repository (currently there is NetworkManager-0.9.9.0-29.git20140131.fc20).
Positive or negative feedback is welcomed. Thanks.
[1] http://copr.fedoraproject.org/coprs/jgrulich/plasma-nm/
Cheers, Jan
Now on my desktop with:
NetworkManager-0.9.9.0-30.git20131003.fc20.x86_64 kde-plasma-nm-0.9.3.3-2.201402137586912.fc20.x86_64 libnm-qt-0.9.9.0-2.20140213d053b27.fc20.x86_64 libmm-qt-1.2.0-1.20140106gitac3f564.fc20.x86_64
I get a completely blank window except for the control buttons across the top. Does it no longer show "system" connections?
That's because the new NetworkManager update is based on older git snapshot, so it doesn't have some stuff we need from the previous version. You can downgrade to the previous version of NetworkManager or kde-plasma-nm and wait for the next NetworkManager update.
STATE CONNECTIVITY WIFI-HW WIFI WWAN-HW WWAN connected full enabled enabled enabled disabled $ nmcli c NAME UUID TYPE TIMESTAMP-REAL cora-client 62b18ffa-6d34-4b09-970f-8146abe27a9b vpn never
CORA b80647f2-abec-439a-9459-d79cd56c6f86 802-11-wireless never
System eth0 5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03 802-3-ethernet Fri 21 Feb 2014 08:50:35 AM MST $ nmcli c show active NAME UUID DEVICES DEFAULT VPN MASTER-PATH System eth0 5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03 eth0 yes no --
Cheers, Jan
On Friday 21 of February 2014 18:02 Jan Grulich wrote:
On Friday 21 of February 2014 08:53 Orion Poplawski wrote:
On 02/10/2014 07:40 AM, Jan Grulich wrote:
Hi,
we've prepared testing builds of kde-plasma-nm including libnm-qt and libmm-qt libraries in COPR repository [1]. The testing version includes a new design and few bugfixes and it is almost ready for stable release, we are just polishing its design. If you want to try it, just add the COPR repository and run update of kde-plasma-nm together with libnm-qt and libmm-qt and you also need to update NetworkManager from updates-testing repository (currently there is NetworkManager-0.9.9.0-29.git20140131.fc20).
Positive or negative feedback is welcomed. Thanks.
[1] http://copr.fedoraproject.org/coprs/jgrulich/plasma-nm/
Cheers, Jan
Now on my desktop with:
NetworkManager-0.9.9.0-30.git20131003.fc20.x86_64 kde-plasma-nm-0.9.3.3-2.201402137586912.fc20.x86_64 libnm-qt-0.9.9.0-2.20140213d053b27.fc20.x86_64 libmm-qt-1.2.0-1.20140106gitac3f564.fc20.x86_64
I get a completely blank window except for the control buttons across the top. Does it no longer show "system" connections?
That's because the new NetworkManager update is based on older git snapshot, so it doesn't have some stuff we need from the previous version. You can downgrade to the previous version of NetworkManager or kde-plasma-nm and wait for the next NetworkManager update.
STATE CONNECTIVITY WIFI-HW WIFI WWAN-HW WWAN connected full enabled enabled enabled disabled $ nmcli c NAME UUID TYPE TIMESTAMP-REAL cora-client 62b18ffa-6d34-4b09-970f-8146abe27a9b vpn never
CORA b80647f2-abec-439a-9459-d79cd56c6f86 802-11-wireless never
System eth0 5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03 802-3-ethernet Fri 21 Feb 2014 08:50:35 AM MST $ nmcli c show active NAME UUID DEVICES DEFAULT VPN MASTER-PATH System eth0 5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03 eth0 yes no --
Cheers, Jan
New update of NetworkManager is already in updates-testing, so it should work again. I'm also already preparing a new update of plasma-nm, but to Fedora repositories, so you don't need to use COPR builds, there will be probably some unstable changes.
Jan
Hi,
I just updated testing builds of plasma-nm to a new git snapshot of development version. There are some new small features, but also a new model with network connections, so it's possible there are some bugs. We would be extremely happy if you can test it and report all your issues. Do not forget to update also libnm-qt/libmm-qt libraries when doing update of plasma-nm.
COPR repository link - http://copr.fedoraproject.org/coprs/jgrulich/plasma-nm/
Cheers, Jan
On 03/04/14 21:50, Jan Grulich wrote:
Hi,
I just updated testing builds of plasma-nm to a new git snapshot of development version. There are some new small features, but also a new model with network connections, so it's possible there are some bugs. We would be extremely happy if you can test it and report all your issues. Do not forget to update also libnm-qt/libmm-qt libraries when doing update of plasma-nm.
COPR repository link - http://copr.fedoraproject.org/coprs/jgrulich/plasma-nm/
Thanks....
The latest version fixes https://bugzilla.redhat.com/show_bug.cgi?id=1049135
One suggestion. When the user clicks on the check-mark to disable wireless the check remains until the actual interfaces are disabled. It seems the time it takes to disable the interfaces can be several seconds. Still seeing the check may cause the user to think their mouse click wasn't received and click it again and again.....
Hi,
Could you remove the ModemManager dependency in libmm-qt, like what was done in libmm-qt-1.0.1-1.fc20.x86_64 ?
I see one regression : the total "Received"/"Transmitted" below the graph alternate between the right value and 0.
libmm-qt-1.2.0-1.20140106gitac3f564.fc20.x86_64 libnm-qt-0.9.9.1-1.20140225b7f3d65.fc20.x86_60 kde-plasma-nm-0.9.3.4-1.20140304e2923f8.fc20.x86_64 NetworkManager-0.9.9.0-31.git20131003.fc20.x86_64
On Wednesday 05 of March 2014 03:18 Loïc Yhuel wrote:
Hi,
Could you remove the ModemManager dependency in libmm-qt, like what was done in libmm-qt-1.0.1-1.fc20.x86_64 ?
I see one regression : the total "Received"/"Transmitted" below the graph alternate between the right value and 0.
libmm-qt-1.2.0-1.20140106gitac3f564.fc20.x86_64 libnm-qt-0.9.9.1-1.20140225b7f3d65.fc20.x86_60 kde-plasma-nm-0.9.3.4-1.20140304e2923f8.fc20.x86_64 NetworkManager-0.9.9.0-31.git20131003.fc20.x86_64
Hi,
sure, I'll remove it. Thanks for the report, that's weird, because it worked before, I'll look at it.
Cheers, Jan
-
Ed Greshko -
Jan Grulich -
José Abílio Matos -
Kevin Kofler -
Loïc Yhuel -
Orion Poplawski