Bug 294292

Raised severity to "Blocker" as requested by Coolo.

For me, this also happens with the DVD installation. This error occured on a normal workstation as well as on a Laptop and therefore does not semm to depend on the hardware.

I've seen it with CDs even in qemu.

Stano, any idea?

Let's get YaST logs for a start. The best would be one exactly at the point of the black screen.

I cannot reproduce it myself :(

BTW, have you been waiting for some time without interaction with the machine?

This might be just console blanking.

Definitely not. I can reproduce it on about all machines I use to install (including qemu instances), but not all the time. And Frank can reproduce it on all his machines.

I'll try to get a yast2 log today

Also, a list of running processes might be useful. 

Of I can't reproduce it now that I'm on NEEDINFO :)

But whenever I can reproduce it the system clock is set to Localtime and now it's always UTC. What configures the value of that combobox? Perhaps it's the 2 hours that the clock is set into the past on UTC->Localtime that triggers the screensaver.

Jiri, this seems to be an issue with setting the clock.

/me thinks Stano must be joking...

Stefan, isn't the difference of the machines able and not able to reproduce the problem the presense of Windows on some of them?

Anyway, I really can't do anything without the logs. And I doubt this is a YaST problem, since there was no change of timezone/clock settings in 10.3 so far.

Rastislav, are you able to reproduce and acquire YaST log files (see
http://en.opensuse.org/Bugs/YaST#I_reported_a_YaST2_bug.2C_and_now_I_am_asked_to_.22attach_y2logs.22._What_does_that_mean.2C_and_how_do_I_do_that.3F)
?

Steffen, wasn't screensaver configuration changed in the inst-sys somehow? Or is there any difference between CD and DVD version?

No, it's unchanged for quite some time AFAIK (which need not mean it is
correct).

The easiest way to reproduce (and this is why it hits me all the time) is
to have the BIOS clock run GMT. As for some obscure reason the timezone
dialog defaults to local time now, I always get a blank screen (and think
yast crashed).

Oh, you can reproduce it as well? So, could you please attach y2logs?

YaST should default to local time only when windows partition is present - Thomas, isn't there a bug in the detection function? The check is "if (size (Storage::GetWinPrimPartitions(Storage::GetTargetMap()))>0) ..."

Isn't this a duplicate of #288859 or #221272?

Maybe it is connected to changed mounting of NTFS partition in alpha6.
Need y2log files to say more.

Yes, this seems to be a duplicate of #221272

I'm not sure, at least this part from comment 12:

"As for some obscure reason the timezone dialog defaults to local time now,"

seems to be related to partitioner.

To decide if this is correct or not, one would need y2log files.

localtime/UTC is dependent on the existence of another OS (OS2 or windows) 
on the system, if another system is detected, time is set to local time
otherwise time is set to UTC.

So maybe this is the reason that it happens on some systems and not on
others.

Please don't get side-tracked. The problem is the screen blanking, not
the timezone dialog (I do have a windows partition, btw). It can
default to Newzealand time for all I care, but I don't want the screen
to go black during installation.

Ah, so if you have windows partition, it is no surprise the time setting defaults to localtime. I thought that the detection of windows partition might be wrong. \

Anyway - Steffen, don't you have the log files?

No, unfortunately not. I saw it during my linuxrc tests; I'll think of
getting a log next time.

Created attachment 154529 [details]
here you are. i hope it is what you need.

Here yast2-storage (AFAIK correctly) detects a windows partition on /dev/sda1
which causes timezone dialog to default to local time.
This causes a jump of the system time by 4 hours into the future (can easily
be seen in the log file) since the timezone is changed from US/Eastern 
(default for english language) to Europe/Bratislava. 
AFAIK this jump in system time does not  happen if local time is not used. 
So question is if and why there is a screensaver active at this part of installation where system time can (and will inevitably under these 
circumstances) jump around.

> AFAIK this jump in system time does not  happen if local time is not used.

Well, not really - in fact it can skip, but for different reason. In this case it was after /sbin/hwclock --hctosys --localtime (adapting system time to hardware clock) but in case you are using utc, it will skip on the change of the timezone (which reminds me that the zic call is useless in case of local time, as seen at line starting with "2007-07-25 02:05:00")

Couldn't the screensaver be enabled after the timezone settings?

Stefan, could I temporary disable DPMS somehow just before the clock change to prevent screen blank at that time?

(I'm referring to bug 221272)

Stefan is on vacation - but it looks like he'll be back tomorrow.

But you can xset -dpms and xset +dpms

Hm, quick test shows that it is easily reproducible and that xset call seems to fix the problem. Steffen, could you include xset and required libraries in the inst-sys?

Please give back to me when you are ready. I'll attach patch for module from yast2-country in case you want to test it.

Created attachment 155159 [details]
patch for /usr/share/YaST2/modules/Timezone.ycp

after applying patch it is necessary to run ycpc -c /usr/share/YaST2/modules/Timezone.ycp

So, i've installed aplha 7.
During installation of KDE cd installation medium i got black screen before(not after)
"Clock and Time Zone" and after restart, before "Password for the System
Administrator root" again.

Created attachment 155305 [details]
here you are y2logs of alpha 7

There was no change in yast2 modules (regarding this bug) for alpha7.

xset added

Reopening to get YaST part of the fix.

Yes, indeed. Just tested for beta1 and it still didn't work.

xset called in yast2-country-2.15.16

i've just installed KDE cd Beta1 and installation went without any problem.it has worked perfect:-)
regards