[opensuse-factory] NetworkManager getting fixed in time for GM release of 12.3

newer
[opensuse-factory] tumbleweed :...

older
Re: [opensuse-factory] why are raw...

Roman Bysh

1 Mar 2013 1 Mar '13

16:27

Hello all, I've installed openSUSE 12.3 RC2 on my desktop.Does any one know if the plasmoid-networkmanagement will be working in time for the final release? Now that I've already set it up under YaST. I have an ethernet cable connected to my desktop. However, under the "Wired" tab nothing appears. It should show "Wired connection 1". -- Cheers! Roman ------------------------------------------- openSUSE -- Get it! Discover it! Share it! ------------------------------------------- http://linuxcounter.net/ #179293 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Show replies by date

Freek de Kruijf

1 Mar 1 Mar

17:04

Op vrijdag 1 maart 2013 11:27:54 schreef Roman Bysh:

...

Hello all,

I've installed openSUSE 12.3 RC2 on my desktop.Does any one know if the plasmoid-networkmanagement will be working in time for the final release?

Now that I've already set it up under YaST.

I have an ethernet cable connected to my desktop. However, under the "Wired" tab nothing appears. It should show "Wired connection 1".

I installed it using the DVD image of RC2 in a VM, which is comparable with your type of installation in my experience, and got the network mode Traditional Method with ifup. In that case you can start the plasmoid, but you don't get anything under "Wired". So check with "systemctl -p Id show network.service" the status, see the release notes for further information. If you get Id=NetworkManager.service maybe a reboot and starting the plasmoid may give you the possibility to configure the network using NetworkManager. If not, you get Id=network.service, the procedure given in the release notes to really change to NetworkManager may work. This does not work in YaST. In my view the network module of YaST still lacks the proper functionality to switch between the Traditional and NetworkManager method. Also the description in the Release Notes is not very clear. It should state that the network module of YaST currently is unable to change from Traditional to NetworkManager and vice versa. So if you want to do that you can the use the procedure given in the Release Notes if it works. I still have not fully tested it. -- 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

Freek de Kruijf

20:18

New subject: [opensuse-factory] NetworkManager getting fixed in time for GM release of 12.3 [problem found]

Op vrijdag 1 maart 2013 18:04:28 schreef u:

...

Op vrijdag 1 maart 2013 11:27:54 schreef Roman Bysh:

...
Hello all,

I've installed openSUSE 12.3 RC2 on my desktop.Does any one know if the plasmoid-networkmanagement will be working in time for the final release?

Now that I've already set it up under YaST.

I have an ethernet cable connected to my desktop. However, under the "Wired" tab nothing appears. It should show "Wired connection 1".

I installed it using the DVD image of RC2 in a VM, which is comparable with your type of installation in my experience, and got the network mode Traditional Method with ifup. In that case you can start the plasmoid, but you don't get anything under "Wired". So check with "systemctl -p Id show network.service" the status, see the release notes for further information. If you get Id=NetworkManager.service maybe a reboot and starting the plasmoid may give you the possibility to configure the network using NetworkManager. If not, you get Id=network.service, the procedure given in the release notes to really change to NetworkManager may work. This does not work in YaST.

In my view the network module of YaST still lacks the proper functionality to switch between the Traditional and NetworkManager method. Also the description in the Release Notes is not very clear. It should state that the network module of YaST currently is unable to change from Traditional to NetworkManager and vice versa. So if you want to do that you can the use the procedure given in the Release Notes if it works. I still have not fully tested it.

After some digging in the log file /var/log/y2log I found the error which causes the problem of not changing the network.service from pointing to NetworkManager.service or just to itself (/etc/init.d/network). When only changing from Traditional to NetworkManager the network module of YaST sets this in the configuration and issues a "/bin/systemctl reload network.service" which does not work. The error message is "Job type reload is not applicable for unit network.service". YaST does not issue an error message to the user. So this error gets unnoticed. For the maintainer: Line 570 in modules/Lan.ycp needs a more complicated treatment. Now it just reads: Service::Reload("network"); without any error checking. -- 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

Mantrid

23:16

New subject: [opensuse-factory] NetworkManager getting fixed in time for GM release of 12.3 [problem found]

On Fri 01 Mar 2013 03:18:28 PM EST, Freek de Kruijf wrote:

...

Op vrijdag 1 maart 2013 18:04:28 schreef u:

...
Op vrijdag 1 maart 2013 11:27:54 schreef Roman Bysh:

...
Hello all,

I've installed openSUSE 12.3 RC2 on my desktop.Does any one know if the plasmoid-networkmanagement will be working in time for the final release?

Now that I've already set it up under YaST.

I have an ethernet cable connected to my desktop. However, under the "Wired" tab nothing appears. It should show "Wired connection 1".

I installed it using the DVD image of RC2 in a VM, which is comparable with your type of installation in my experience, and got the network mode Traditional Method with ifup. In that case you can start the plasmoid, but you don't get anything under "Wired". So check with "systemctl -p Id show network.service" the status, see the release notes for further information. If you get Id=NetworkManager.service maybe a reboot and starting the plasmoid may give you the possibility to configure the network using NetworkManager. If not, you get Id=network.service, the procedure given in the release notes to really change to NetworkManager may work. This does not work in YaST.

In my view the network module of YaST still lacks the proper functionality to switch between the Traditional and NetworkManager method. Also the description in the Release Notes is not very clear. It should state that the network module of YaST currently is unable to change from Traditional to NetworkManager and vice versa. So if you want to do that you can the use the procedure given in the Release Notes if it works. I still have not fully tested it.

After some digging in the log file /var/log/y2log I found the error which causes the problem of not changing the network.service from pointing to NetworkManager.service or just to itself (/etc/init.d/network).

When only changing from Traditional to NetworkManager the network module of YaST sets this in the configuration and issues a "/bin/systemctl reload network.service" which does not work. The error message is "Job type reload is not applicable for unit network.service". YaST does not issue an error message to the user. So this error gets unnoticed.

For the maintainer: Line 570 in modules/Lan.ycp needs a more complicated treatment. Now it just reads: Service::Reload("network"); without any error checking.

Here's what I did to enable the Network Manager. To enable NetworkManager, use: systemctl stop network.service systemctl --force enable NetworkManager.service systemctl start network.service Cheers! Roman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Roman Bysh

23:22

New subject: [opensuse-factory] NetworkManager getting fixed in time for GM release of 12.3 [problem found]

On 03/01/2013 06:16 PM, Mantrid wrote:

...

On Fri 01 Mar 2013 03:18:28 PM EST, Freek de Kruijf wrote:

...
Op vrijdag 1 maart 2013 18:04:28 schreef u:

...
Op vrijdag 1 maart 2013 11:27:54 schreef Roman Bysh:

...
Hello all,

I've installed openSUSE 12.3 RC2 on my desktop.Does any one know if the plasmoid-networkmanagement will be working in time for the final release?

Now that I've already set it up under YaST.

I have an ethernet cable connected to my desktop. However, under the "Wired" tab nothing appears. It should show "Wired connection 1".

I installed it using the DVD image of RC2 in a VM, which is comparable with your type of installation in my experience, and got the network mode Traditional Method with ifup. In that case you can start the plasmoid, but you don't get anything under "Wired". So check with "systemctl -p Id show network.service" the status, see the release notes for further information. If you get Id=NetworkManager.service maybe a reboot and starting the plasmoid may give you the possibility to configure the network using NetworkManager. If not, you get Id=network.service, the procedure given in the release notes to really change to NetworkManager may work. This does not work in YaST.

In my view the network module of YaST still lacks the proper functionality to switch between the Traditional and NetworkManager method. Also the description in the Release Notes is not very clear. It should state that the network module of YaST currently is unable to change from Traditional to NetworkManager and vice versa. So if you want to do that you can the use the procedure given in the Release Notes if it works. I still have not fully tested it.

After some digging in the log file /var/log/y2log I found the error which causes the problem of not changing the network.service from pointing to NetworkManager.service or just to itself (/etc/init.d/network).

When only changing from Traditional to NetworkManager the network module of YaST sets this in the configuration and issues a "/bin/systemctl reload network.service" which does not work. The error message is "Job type reload is not applicable for unit network.service". YaST does not issue an error message to the user. So this error gets unnoticed.

For the maintainer: Line 570 in modules/Lan.ycp needs a more complicated treatment. Now it just reads: Service::Reload("network"); without any error checking.

Here's what I did to enable the Network Manager.

To enable NetworkManager, use:

systemctl stop network.service systemctl --force enable NetworkManager.service systemctl start network.service

Cheers!

Roman

BTW I can now see the network management icon. -- Cheers! Roman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Andrey Borzenkov

2 Mar 2 Mar

04:25

New subject: [opensuse-factory] NetworkManager getting fixed in time for GM release of 12.3 [problem found]

В Fri, 01 Mar 2013 21:18:28 +0100 Freek de Kruijf пишет:

...

Op vrijdag 1 maart 2013 18:04:28 schreef u:

...
Op vrijdag 1 maart 2013 11:27:54 schreef Roman Bysh:

...
Hello all,

I've installed openSUSE 12.3 RC2 on my desktop.Does any one know if the plasmoid-networkmanagement will be working in time for the final release?

Now that I've already set it up under YaST.

I have an ethernet cable connected to my desktop. However, under the "Wired" tab nothing appears. It should show "Wired connection 1".

I installed it using the DVD image of RC2 in a VM, which is comparable with your type of installation in my experience, and got the network mode Traditional Method with ifup. In that case you can start the plasmoid, but you don't get anything under "Wired". So check with "systemctl -p Id show network.service" the status, see the release notes for further information. If you get Id=NetworkManager.service maybe a reboot and starting the plasmoid may give you the possibility to configure the network using NetworkManager. If not, you get Id=network.service, the procedure given in the release notes to really change to NetworkManager may work. This does not work in YaST.

In my view the network module of YaST still lacks the proper functionality to switch between the Traditional and NetworkManager method. Also the description in the Release Notes is not very clear. It should state that the network module of YaST currently is unable to change from Traditional to NetworkManager and vice versa. So if you want to do that you can the use the procedure given in the Release Notes if it works. I still have not fully tested it.

After some digging in the log file /var/log/y2log I found the error which causes the problem of not changing the network.service from pointing to NetworkManager.service or just to itself (/etc/init.d/network).

When only changing from Traditional to NetworkManager the network module of YaST sets this in the configuration and issues a "/bin/systemctl reload network.service" which does not work. The error message is "Job type reload is not applicable for unit network.service". YaST does not issue an error message to the user. So this error gets unnoticed.

For the maintainer: Line 570 in modules/Lan.ycp needs a more complicated treatment. Now it just reads: Service::Reload("network"); without any error checking.

Did you report it to bugzilla? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Freek de Kruijf

09:31

New subject: [opensuse-factory] NetworkManager getting fixed in time for GM release of 12.3 [problem found]

Op zaterdag 2 maart 2013 08:25:30 schreef Andrey Borzenkov:

...

В Fri, 01 Mar 2013 21:18:28 +0100

Freek de Kruijf пишет:

...
Op vrijdag 1 maart 2013 18:04:28 schreef u:

...
Op vrijdag 1 maart 2013 11:27:54 schreef Roman Bysh:

...
Hello all,

I've installed openSUSE 12.3 RC2 on my desktop.Does any one know if the plasmoid-networkmanagement will be working in time for the final release?

Now that I've already set it up under YaST.

I have an ethernet cable connected to my desktop. However, under the "Wired" tab nothing appears. It should show "Wired connection 1".

I installed it using the DVD image of RC2 in a VM, which is comparable with your type of installation in my experience, and got the network mode Traditional Method with ifup. In that case you can start the plasmoid, but you don't get anything under "Wired". So check with "systemctl -p Id show network.service" the status, see the release notes for further information. If you get Id=NetworkManager.service maybe a reboot and starting the plasmoid may give you the possibility to configure the network using NetworkManager. If not, you get Id=network.service, the procedure given in the release notes to really change to NetworkManager may work. This does not work in YaST.

In my view the network module of YaST still lacks the proper functionality to switch between the Traditional and NetworkManager method. Also the description in the Release Notes is not very clear. It should state that the network module of YaST currently is unable to change from Traditional to NetworkManager and vice versa. So if you want to do that you can the use the procedure given in the Release Notes if it works. I still have not fully tested it.

After some digging in the log file /var/log/y2log I found the error which causes the problem of not changing the network.service from pointing to NetworkManager.service or just to itself (/etc/init.d/network).

When only changing from Traditional to NetworkManager the network module of YaST sets this in the configuration and issues a "/bin/systemctl reload network.service" which does not work. The error message is "Job type reload is not applicable for unit network.service". YaST does not issue an error message to the user. So this error gets unnoticed.

For the maintainer: Line 570 in modules/Lan.ycp needs a more complicated

treatment. Now it just reads: Service::Reload("network");

without any error checking.

Did you report it to bugzilla?

Yes, as a follow up see https://bugzilla.novell.com/show_bug.cgi?id=798348#c33 -- 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

4073

Age (days ago)

4074

Last active (days ago)

List overview

Download

6 comments

4 participants

participants (4)

Andrey Borzenkov
Freek de Kruijf
Mantrid
Roman Bysh