Op maandag 11 februari 2013 13:02:29 schreef Graham P Davis:

On Mon, 11 Feb 2013 12:17:22 +0100

Freek de Kruijf wrote:

...

Starting networkmanager as a user makes it possible to change parameters, so apparently NetworkManager is active. However there is no icon in the task bar afrter the start.

I found that I had to re-create ~/.kde4/share/config/plasma-desktop-appletsrc in order to get the icon to appear in the systray. I assume renamimg it and logging off and on will do the trick but I went the long way round as I started by renaming ~/.kde4/ to check that the problem was located in that area.

That worked, but still it is a bug which needs to be solved. I also installed RC1 on my laptop where YaST2 choose NetworkManager as the method to manage the network. However on first login I did not have the icon and after starting the UI for NetworkManager I could not do anything with Wireless, the tab label remained grey. To my surprise I changed the YaST2 configuration to the Traditional method with ifup, logged out and in, and then I did see the icon and I am able to activate the wireless connection. And still the configuration of YaST2 is the traditional method. I wonder what the situation will be after a reboot. -- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Op woensdag 13 februari 2013 11:04:07 schreef u:

On Monday 11 February 2013 17:57:48 Freek de Kruijf wrote:

...

Op maandag 11 februari 2013 13:02:29 schreef Graham P Davis:

...

On Mon, 11 Feb 2013 12:17:22 +0100

Freek de Kruijf wrote:

...

Starting networkmanager as a user makes it possible to change parameters, so apparently NetworkManager is active. However there is no icon in the task bar afrter the start.

I found that I had to re-create ~/.kde4/share/config/plasma-desktop-appletsrc in order to get the icon to appear in the systray. I assume renamimg it and logging off and on will do the trick but I went the long way round as I started by renaming ~/.kde4/ to check that the problem was located in that area.

That worked, but still it is a bug which needs to be solved.

I also installed RC1 on my laptop where YaST2 choose NetworkManager as the method to manage the network. However on first login I did not have the icon and after starting the UI for NetworkManager I could not do anything with Wireless, the tab label remained grey.

To my surprise I changed the YaST2 configuration to the Traditional method with ifup, logged out and in, and then I did see the icon and I am able to activate the wireless connection. And still the configuration of YaST2 is the traditional method. I wonder what the situation will be after a reboot.

There are some issues with the network thingy, I'm experiencing this too. I'm not sure if anyone is working on it, ???

Did a new installation using the DVD. This was in a VM with a virtual Ethernet interface. YaST2 chooses the traditional method for the network configuration. During the installation the test for a network connection showed a failed connection due to an error returned when YaST2 apparently performed an ifup command. Whatever the status of the network configuration is in YaST2 ifup/down always gives an error message telling the network is managed by the NetworkManager. Going back in the installation and changing to Managed by NetworkManager the test returned OK and I finished the installation. However still no icon in the task bar. Furthermore when I have IPv6 set up for eth0 as Basic Settings and Method Automatic and any choice for Privacy Extensions, the network connection is unstable and is initialized each 45 seconds. The reason is that DHCPv6 packets are filtered by the firewall. This is an older unsolved bug https://bugzilla.novell.com/show_bug.cgi?id=778434 One needs to enter a line FW_SERVICES_ACCEPT_EXT="fe80::/64,udp,546,547" in the file /etc/sysconfig/SuSEfirewall2 which allows these packets in the system. This quite safe as it allows only these udp packets from the local link. -- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org