Bug 991382

Summary:	yast2-network: internal error on entering wlan access point information
Product:	[openSUSE] openSUSE Tumbleweed	Reporter:	Dirk Mueller <dmueller>
Component:	YaST2	Assignee:	Michal Filka <mfilka>
Status:	RESOLVED FIXED	QA Contact:	Jiri Srain <jsrain>
Severity:	Normal
Priority:	P5 - None	CC:	ada.lovelace, dmueller, igonzalezsosa, kanderssen, mfilka
Version:	Current
Target Milestone:	---
Hardware:	Other
OS:	Other
URL:	https://trello.com/c/a45bxiln/634-1-sle-12-sp2-991382-yast2-network-internal-error-on-entering-wlan-access-point-information
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Dirk Mueller 2016-07-30 20:20:37 UTC

When trying to configure a wlan access point (managed mode with WPA-PSK), yast2-network ends in an internal error, something like "no such method .empty? for 0:BigInt" (I don't have infromation here anymore, was helping a fried)

this seems to be caused by https://github.com/yast/yast-network/commit/423e0246f0ee9417714e1116c136fb035dc9248f

Commenting out that code got beyond that error. it looks like the code only expected strings to be passed in, but it seems there are cases where non-strings are also valid.

Comment 3 Michal Filka 2016-08-02 12:07:59 UTC

I was somehow able to reproduce the issue. However I was not able to reproduce it by using UI (I did some manual hacks).

1) Did you do just wireless configuration (ESSID, WPA, ...) or something more?
2) What wireless options did you try to configure? What values did you enter (just alpha numeric strings or some special chars)?
3) Did you add new or edit existing configuration?
4) Was the error raised right after finishing the wireless card configuration (I assume that yes, but lets make it clear) or when saving whole network configuration?
5) What environment was used (ncurses / Qt)?

Comment 4 Michal Filka 2016-08-02 12:23:37 UTC

ok, one more question / note.

Only case when I'm able to reproduce similar issue is unrelated to wireless. In particular I get similar internal error when I use "Device activation" mode named "On Cable Connection" (aka ifplugd in STARTMODE option in ifcfg).

Did you use same configuration? 

Thanks

Comment 6 Michal Filka 2016-08-11 16:16:49 UTC

The patch which solves issue from comment#4 was merged in yast2-network 3.1.160

Comment 7 Michal Filka 2016-08-15 07:44:00 UTC

No additional info provided. Proposed patch already merged. Feel free to reopen if you can still reproduce the issue. 

Thanks for reporting.

Comment 8 Michal Filka 2016-08-22 08:10:21 UTC

*** Bug 992516 has been marked as a duplicate of this bug. ***