>> The very first line is:
>>
>> 2017-09-15 10:55:29 <1> linux(19818) [Ruby] bin/y2start:16 y2base
>> called with ["firstboot", "--arg", "firstboot", "ncurses"]
> check y2start log, it should print why it pick ncurses as UI
I see this in y2start.log:
|-- Starting X11/VNC based session...
Stage [call]: Starting prequalification checks...
Stage [call]: ===================================
|-- No testX binary installed -> Medium Qt disabled
|-- No SSH daemon running -> Medium SSH disabled
|-- No testX binary installed -> Medium VNC disabled
Stage [call]: Evaluate medium selection...
Stage [call]: ============================
Stage [call]: Check selected medium...
Stage [call]: ========================
|-- Wished medium is: QT
|-- Medium Qt not available, falling back to ncurses
|-- Selected medium is: NCURSES
testX? What's that? X11 and Qt are installed. As is
yast2-control-center-qt. I have no idea what might be missing.
>> 2017-09-15 11:05:01 <1> linux(19818) [Ruby] modules/Misc.rb:188
>> .sysconfig.firstboot.LICENSE_REFUSAL_ACTION: 'halt'
>> 2017-09-15 11:05:01 <1> linux(19818) [Ruby] clients/firstboot.rb:95
>> Firstboot aborted, LICENSE_REFUSAL_ACTION: halt
>> 2017-09-15 11:05:01 <1> linux(19818) [Ruby] clients/firstboot.rb:101
>> Halting the system...
>>
>> I have no idea why. The only thing the firstboot has related to a
>> license is:
>>
>> <module>
>> <enabled config:type="boolean">false</enabled>
>> <label>License Agreement</label>
>> <name>firstboot_license</name>
>> </module>
>>
>> So it is not enabled. Perhaps that is not the way to do this?
>
> Well, so what happen here? sysconfig for first boot is set to halt if
> license is not approved and license dialog is disabled, so you cannot
> approve it. So it halt.
I will change that.
This is different behavior than before (i.e., 13.1.... I know...) . I
had this clause when it worked. I am happy to make changes as needed.
But I don't know where to find documentation. I see lots on making my
own YaST modules and all. But not on using existing ones in firstboot.
Like I say, I do not think there are bugs in YaST. Just in my attempted use...
--
Roger Oberholtzer
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]
