Selecting "Text Mode" from the linuxrc menu works (but this doesn't use
fbiterm and therefore CJK won't work).

But when entering "textmode=1" on the command line the installation
stops with the message

    "An error occured during the installtion"

in a red box.

I switched to console 2 and checked that fbiterm was available and
could be started, i.e. fbiterm is not causing the problem.

Then, trying to start YaST2 manually, I found:

cd /usr/lib/YaST2/bin
./y2base installation '("initial")' ncurses --nothreads
Error loading language plugin /usr/lib64/YaST2/plugin/libpy2lang_perl.so: libgobject-2.0.so.0: cannot open shared object file: No such file or directory.

ldd /usr/lib64/YaST2/plugin/libpy2lang_perl.so
[...]
libgobject-2.0.so.0 => not found

/etc/ld.so.conf contains /opt/gnome/lib64 which is the directory where
libgobject-2.0.so.0 lives.

Calling "ldconfig" once fixes the problem, after doing that,

    cd /usr/lib/YaST2/bin
    ./y2base installation '("initial")' ncurses --nothreads

starts YaST2.

interestingly, we already run ldconfig before yast is started

Reassigned to Steffen as the linuxrc maintainer.

I've not the slightest idea what I have to do with this.

Mike, which build did you use? It looks to me like an inconsistent build. Can you check it again? And if it fails, check whether the libgobject-2.0.so.0 really exists?

Jiri Srain> Mike, which build did you use? It looks to me like an inconsistent
Jiri Srain> build. Can you check it again?

I just tried once more with the Goldmaster.
The behaviour is still the same, i.e. the bug still exists.

Jiri Srain> And if it fails, check whether the
Jiri Srain> libgobject-2.0.so.0 really exists?

Yes, libgobject-2.0.so.0 exists in /opt/gnome/lib64.

You need to use textmode=1 *and* lang=ja (i.e. Japanese).

-> yast2-perl-bindings to investigate

I have tried with an x86_64 DVD alpha from Jan 31 and text mode Japanese YaST does come up.

Please reopen if it still happens.

With today's (Feb 13) factory:
- Japanese and Text mode results in 80x25 VGA ncurses mode with lots of ??
- Japanese and VESA mode results in 800x600 QT/yast2
- Japanese and "textmode=1" and 1024x768 mode results in 1024x768 FB (good)

But how is one supposed to pass textmode=1? It would be easier if selecting Text mode in the bootloader did The Right Thing.

'text mode' always goes for plain vga. Basically to give people with broken
fb support a chance. And, it is needed to see the early kernel messages
(in case it breaks that early).

IMO people that go for ncurses while they could as well just use the qt interface clearly indicate that they are not the ones that like the easy way.
So they are probably overjoyed to have to type that parameter by hand.
Don't you think?