1059301 – "yast network" crashes when trying to change a network interface

Bug 1059301 - "yast network" crashes when trying to change a network interface

Summary: "yast network" crashes when trying to change a network interface

Status:	RESOLVED DUPLICATE of bug 1054448

Alias:	None

Product:	openSUSE Tumbleweed
Classification:	openSUSE
Component:	YaST2 (show other bugs)
Version:	Current
Hardware:	x86-64 openSUSE Factory

Priority:	P5 - None Severity: Normal (vote)
Target Milestone:	---
Assignee:	E-mail List
QA Contact:	Jiri Srain

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Clone This Bug

Reported:	2017-09-19 08:30 UTC by Freek de Kruijf
Modified:	2017-09-20 12:01 UTC (History)
CC List:	1 user (show)

See Also:
Found By:	---
Services Priority:
Business Priority:
Blocker:	---
Marketing QA Status:	---
IT Deployment:	---

Attachments
y2log (124.51 KB, text/plain) 2017-09-19 08:30 UTC, Freek de Kruijf	Details
screen after choosing Launch (56.94 KB, image/png) 2017-09-19 08:36 UTC, Freek de Kruijf	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Freek de Kruijf 2017-09-19 08:30:47 UTC

Created attachment 741039 [details]
y2log

Giving the command "yast network" in a console I get the ncurses screen. Starting Launch I get the screen in the first attachment. Currently I can't reproduce the crash. Anyway as can be seen from the screen dump the page is distorted. Maybe caused by the dialog application. See other bug report #1059297.
I include the y2log produced before I saw the crash and trying to reproduce the crash. It shows errors. Messages are sometimes in Dutch.

Comment 1 Freek de Kruijf 2017-09-19 08:36:15 UTC

Created attachment 741040 [details]
screen after choosing Launch

As can be seen lines are not properly shown. A question mark in reverse shows where a line should be drawn, etc. See the bug report mentioned on even worse distortions.

Comment 2 José Iván López González 2017-09-20 12:01:03 UTC

Duplicate of 1054448.

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