Bug 904020

Summary: Internal error in network settings
Product: [openSUSE] openSUSE Distribution Reporter: Johnny Willemsen <jwillemsen>
Component: YaST2Assignee: Michal Filka <mfilka>
Status: RESOLVED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Major    
Priority: P5 - None CC: jreidinger, jwillemsen, kanderssen
Version: 13.2Flags: mfilka: needinfo? (jwillemsen)
Target Milestone: ---   
Hardware: x86-64   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: Log files created using save_y2logs /tmp/y2logs.tgz

Description Johnny Willemsen 2014-11-05 12:57:35 UTC
After changing the network manager to wicked and now want to set it back I get the following error when starting the YaST2 - Network Settings

Details: undefined method '[]' for nil:NilClass
Caller: /usr/share/YaST2/modules/LanItems.rb:1334 in 'block in BuildLanOverview'
Comment 1 Michal Filka 2014-11-05 17:24:32 UTC
I cannot reproduce that.

@Johnny Willemsen:
did you configure something when the service was switched to wicked? (and what if so)

thanks
Comment 2 Johnny Willemsen 2014-11-05 18:13:48 UTC
I am not sure what I all did, did switch a few times from Network Manager to Wicked, but also once to network services disabled and than to wicked. Did once start the NetworkManager as root by hand. 

After running the instructions as noted on http://doc.opensuse.org/release-notes/x86_64/openSUSE/13.2/ I at least could configure the network again, that fixed the error
Comment 3 Michal Filka 2014-11-06 00:06:43 UTC
1) Do you have YaST logs which covers the "Internal error" state available?
2) Could you provide some more info about your NIC(s)?
3) Could you provide NIC's device name(s)? (eth0, wlan1, enp0s3, .... or your custom name if you used that)
Comment 4 Johnny Willemsen 2014-11-06 07:26:24 UTC
Couldn't find a log file with the error in it, any suggestion which ones you need? 

The network info

em1       Link encap:Ethernet  HWaddr D4:BE:D9:58:C3:3F  
          inet addr:192.168.192.113  Bcast:192.168.192.255  Mask:255.255.255.0
          inet6 addr: fe80::d6be:d9ff:fe58:c33f/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:29914 errors:0 dropped:0 overruns:0 frame:0
          TX packets:22670 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:31182406 (29.7 Mb)  TX bytes:3727611 (3.5 Mb)
          Interrupt:20 Memory:f7700000-f7720000 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:514 errors:0 dropped:0 overruns:0 frame:0
          TX packets:514 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:19402 (18.9 Kb)  TX bytes:19402 (18.9 Kb)

tun0      Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
          inet addr:10.9.0.18  P-t-P:10.9.0.17  Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:9111 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5280 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          RX bytes:10996993 (10.4 Mb)  TX bytes:307457 (300.2 Kb)

wlp3s0    Link encap:Ethernet  HWaddr 84:4B:F5:98:04:C5  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
Comment 5 Michal Filka 2014-11-06 08:33:35 UTC
(In reply to Johnny Willemsen from comment #4)
> Couldn't find a log file with the error in it, any suggestion which ones you
> need? 

you can use save_y2logs (as root), also see:

http://en.opensuse.org/openSUSE:Report_a_YaST_bug
Comment 6 Johnny Willemsen 2014-11-06 09:33:50 UTC
Created attachment 612630 [details]
Log files created using save_y2logs /tmp/y2logs.tgz
Comment 7 Knut Alejandro Anderssen González 2016-10-11 08:03:18 UTC
There has been some fixes related to this bug, and currently is reported or should be related to bugs (907350, 956755, 972575, 982850)

*** This bug has been marked as a duplicate of bug 956755 ***