Bug 960244

Summary:	Partition settings are lost when going back to change the installation language
Product:	[openSUSE] openSUSE Distribution	Reporter:	Forgotten User ZBSnh6gq8B <forgotten_ZBSnh6gq8B>
Component:	Installation	Assignee:	YaST Team <yast-internal>
Status:	RESOLVED WONTFIX	QA Contact:	Jiri Srain <jsrain>
Severity:	Normal
Priority:	P5 - None	CC:	aschnell
Version:	Leap 42.1
Target Milestone:	---
Hardware:	Other
OS:	Other
URL:	https://trello.com/c/2HYghuyh/653-leap-bug-960244-partition-settings-are-lost-when-going-back-to-change-the-installation-language
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Forgotten User ZBSnh6gq8B 2015-12-26 16:36:00 UTC

I started with German as installation language, created a custom partition scheme and continued with the installation steps until the final screen to start the installation appeared.

Then I decided to switch from German to English. I went back switched the language and when clicking next both the partition scheme and the time zone settings were lost. But not the new user settings or the boot loader settings I did. It looks like changing the installation language resets some of the settings, but not all. IMHO the behavior should be consistent for everything - and I suggest it should keep the changes and not reset them, as resetting is an unexpected behavior.

Comment 1 Arvin Schnell 2016-01-08 16:39:19 UTC

Indeed. The partitioning is likely lost since the devices are rescanned
during the second "System Probing".

Comment 2 Arvin Schnell 2016-01-08 16:41:07 UTC

I added a card to the YaST trello task board so that the issue is prioritised
with the other tasks.

Comment 3 Tomáš Chvátal 2018-04-13 15:07:12 UTC

This is automated batch bugzilla cleanup.

The openSUSE 42.1 changed to end-of-life (EOL [1]) status. As such
it is no longer maintained, which means that it will not receive any
further security or bug fix updates.
As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
openSUSE, or you can still observe it under openSUSE Leap 15.0, please
feel free to reopen this bug against that version (see the "Version"
component in the bug fields), or alternatively open
a new ticket.

Thank you for reporting this bug and we are sorry it could not be fixed
during the lifetime of the release.

[1] https://en.opensuse.org/Lifetime