Bug 1179481

Summary:	Have some more information for the UTC device clock setting
Product:	[openSUSE] openSUSE Tumbleweed	Reporter:	Claudius Ellsel <claudius.ellsel>
Component:	YaST2	Assignee:	E-mail List <yast2-maintainers>
Status:	RESOLVED WONTFIX	QA Contact:	Jiri Srain <jsrain>
Severity:	Enhancement
Priority:	P5 - None	CC:	schubi
Version:	Current
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Claudius Ellsel 2020-12-01 15:56:37 UTC

I assume that this setting is relevant for compatibility with parallel installations (most notably Windows). I think it UTC is used for most Linux distributions while Windows doesn't use it by default.

In YaST during installation that option was not selected by default, so I left it like this.

Unfortunately I have changed the Windows default to not have interferences with already existing Linux installations. This caused a one hour offset for Windows after using openSUSE.

So I had to manually turn that setting on in YaST afterwards. Some more information (like Windows uses ... by default, Linux mostly uses ...) would have helped me to prevent this. I also thought about some sort of auto detect mechanism that selects the best value for this setting on installation, but it might be hard to gather the required information for this.

Comment 1 Stefan Hundhammer 2020-12-01 20:13:15 UTC

During installation, we check if there is an existing Windows installation on the machine for that very reason, and that is what determines our default for that value.

IIRC we also have that information you are requesting in the help text.

Comment 2 Claudius Ellsel 2020-12-01 21:04:30 UTC

I already thought that this might be the case. The problem is when somebody changed the Windows installation to be "compliant" with Linux and then YaST changes the Linux default to be compliant with Windows. I know it is thought as a feature and I like that, but unfortunately for my rare case it did not work.

I guess I should have read the help text, then :) I expected some kind of tooltip but that might be annoying.

Comment 3 Stefan Schubert 2020-12-02 12:41:52 UTC

(In reply to Stefan Hundhammer from comment #1)
> During installation, we check if there is an existing Windows installation
> on the machine for that very reason, and that is what determines our default
> for that value.
> 
> IIRC we also have that information you are requesting in the help text.

Thanks Stefan for the answer.
Well Clausius you are right. It is a seldom use case and to be honest I do not
see a realistic chance to take care about it. It is documented in the help text and you have found a "workaround" very quickly which a normal user will find it too.
But I must admit....a nice thought. Thanks for sharing it :-)

Comment 4 Claudius Ellsel 2020-12-02 12:47:42 UTC

Alright, makes sense.