Bug 326899

Created attachment 173735 [details]
SaX.log

Created attachment 173736 [details]
xorg.conf

Created attachment 173737 [details]
yast2log.tgz

The config file does not look like a sax2 created config file at all.

Section "InputDevice"
        Identifier  "MX1000"
	Driver      "evdev"
	Option      "Dev Name" "Logitech, Inc. MX-1000 Cordless Mouse Receiver"
	Option      "evBits" "+1-2"
	Option      "keyBits" "~272-287"
	Option      "relBits" "~0-2 ~6 ~8"
	Option      "Pass" "3"
EndSection

Maybe this is an update from another Linux distribution to openSUSE 10.3? I don't know. This would also explain why nothing works on this machine.

the yast log files look like an installation at least :)

the question remains: how did you create your xorg.conf.

I need access to such system in order to do some tests. It also would
be nice to have the possibility to install packages on the system to be
able to compile sax2 partially 

Created attachment 173812 [details]
sax2 - lspci - xorg.conf - crated with sax2 -ar

1. We have tried some of those http://www.xorg-conf.org/ - failed

2. After system reboot, YaST install tels me that some packages where not installed, but doesent tell what packages - and then "crashed" trying to open X server.

3. Grapghical interface works fine during installation proces, this problem appears after reboot.

I think I did not understand the whole process. You said it crashed
during installation, but from your comments sax2 also crashed while
called within the installed system from runlevel 3.

- The information you have sent is unfortunately not very helpful because
  it doesn't give any information on the crash, no backtrace, etc...
  That's why I asked for access to the system 

- Christian could you tell me if we have such a laptop in our pool.
  If so could you allow me to access such a machine. Thanks

Installation is in 2 steps - first Yast is installing packages, then reboots.

The first process graphical interface was ok, after reboot the text mode of yast apears with message that some packages where not installed. When it was trying go to the hardware configuration step then crashed. After that I was trying use sax2 to rapair this - crashed to.

The only Amilo we have is 'xi 1547'. Don't know if this helps.

according to comment #11 the installation in step 2 seems to be broken
I would suggest to take care for this one first because all other problems
could be a follow up on the first problem. If YaST runs ok in graphics mode
but doesn't in second phase it seems to be a problem of the installation
process

I agree, e.g.:

y2logRPM:
[...]
2007-09-20 16:38:57 sax2-libsax-perl-8.1-249.i586.rpm install failed
rpm output:
error: Failed dependencies:
        libsax.so.7 is needed by sax2-libsax-perl-8.1-249.i586

> 2. After system reboot, YaST install tells me that some packages were not
> installed, but doesent tell which packages - and then "crashed" trying to
> open X server.
>
> 3. Graphical interface works fine during installation proces, 

Files from instsys are used.

> this problem appears after reboot.

Files from installed are used - which fails due to missing packages.

(In reply to comment #14 from Stefan Dirsch)
> y2logRPM:
> [...]
> 2007-09-20 16:38:57 sax2-libsax-perl-8.1-249.i586.rpm install failed
> rpm output:
> error: Failed dependencies:
>         libsax.so.7 is needed by sax2-libsax-perl-8.1-249.i586

And one line later it says:
2007-09-20 16:38:57 sax2-libsax-perl-8.1-249.i586.rpm installed ok
This because of the 3 tries libzypp uses to install a package.

So sax2-libsax-perl is installed properly (line 1357) and so is sax2-libsax (line 1381).

So this is not YaST related.

comment 13 is still valid. YaST doesn't start in graphics mode when 
the second phase starts. This is not sax2 related because it isn't even
called for the initial startup procedure

Daniel, please, check the installation startup scripts:

First stage:
Stage [1]: Starting F09-start...
Stage [1]: =====================
        |-- Creating hook script list: preFirstCall...
        |-- Delegate program call to YaST2.call installation initial
Stage [call]: Starting prequalification checks...
Stage [call]: ===================================
        |-- No Framebuffer available: Using vesa driver
        |-- No SSH daemon running -> Medium SSH disabled
Stage [call]: Evaluate medium selection...
Stage [call]: ============================
Stage [call]: Check selected medium...
Stage [call]: ========================
        |-- Wished medium is: QT
        |-- Selected medium is: QT
        |-- X-Server is ready: 3518
        |-- UI_args: Running in fullscreen mode
        |-- Allow big memory allocation: overcommit_memory=1
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        |-- Starting YaST2:
        |-- MODULE_NAME: installation
        |-- MODE_FLAGS:
        |-- MODULE_ARGS: ("initial")

Second stage:
Stage [2]: Starting S08-start...
Stage [2]: =====================
        |-- Creating hook script list: preSecondCall...
        |-- Starting X11/VNC based session...
Stage [call]: Starting prequalification checks...
Stage [call]: ===================================
        |-- No Framebuffer available: Using vesa driver
        |-- No SSH daemon running -> Medium SSH disabled
Stage [call]: Evaluate medium selection...
Stage [call]: ============================
Stage [call]: Check selected medium...
Stage [call]: ========================
        |-- Wished medium is: QT
        |-- Selected medium is: QT
        |-- UI_args: Running in fullscreen mode
        |-- X-Server couldn't be started, falling back to ncurses
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        |-- Check for FB-I-terminal: RUN_FBITERM = 0
        |-- Allow big memory allocation: overcommit_memory=1
        |-- Starting YaST2:
        |-- MODULE_NAME: installation
        |-- MODE_FLAGS: ("text_fallback")

What is even more strange (second stage-finish):
        |-- YaST procedure ended successfully
        |-- Reset memory allocation: overcommit_memory=0
        |-- Creating hook script list: postSecondCall...
Stage [2]: Starting S09-cleanup...
Stage [2]: =======================
        |-- kill X-Server with PID: 3556
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        |-- Shutdown SSH daemon and network interfaces...

So, wasn't it actually running?

Hmm, or maybe is also something wrong with some X-libs (or other ones):

y2log.SuSEconfig
grep "is truncated" y2log.SuSEconfig >
...
/sbin/ldconfig: file /usr/lib/libgnutls.so.13 is truncated
/sbin/ldconfig: file /usr/lib/libgnutls.so.13.2.2 is truncated
/sbin/ldconfig: file /usr/lib/libXfont.so.1 is truncated
/sbin/ldconfig: file /usr/lib/libXfont.so.1.4.1 is truncated
/sbin/ldconfig: file /usr/lib/liby2storage.so.2 is truncated
/sbin/ldconfig: file /usr/lib/liby2storage.so.2.0.0 is truncated
/sbin/ldconfig: file /usr/lib/libOSMesa.so.6 is truncated
/sbin/ldconfig: file /usr/lib/libOSMesa.so.6.5.3 is truncated
/sbin/ldconfig: file /usr/lib/libsmbclient.so.0 is truncated
...
lines 532-585/585 (END)

There also might have been problem with Qt or Qtlibs (See y2logRPM).

Anyway, definitely NOT MINE ;)
-> back to yast2-maintainers@suse.de

/sbin/ldconfig: file /opt/kde3/lib/libartsgslplayobject.so is truncated
/sbin/ldconfig: file /opt/kde3/lib/libartsgslplayobject.so.0 is truncated
/sbin/ldconfig: file /opt/kde3/lib/libartsgslplayobject.so.0.0.0 is truncated
/sbin/ldconfig: file /opt/kde3/lib/libkhtml.so.4 is truncated
/sbin/ldconfig: file /opt/kde3/lib/libkhtml.so.4.2.0 is truncated
/sbin/ldconfig: file /opt/kde3/lib/libkjs.so.1 is truncated
/sbin/ldconfig: file /opt/kde3/lib/libkjs.so.1.2.0 is truncated
/sbin/ldconfig: file /opt/kde3/lib/libkdeinit_kdesktop.so is truncated
/sbin/ldconfig: file /opt/kde3/lib/libkonq.so is truncated
 .... aso.

There must be something serverely wrong here.

bug #327420  seems to be the same - but due to japanese locale even the interesting logs are in japanese (I ask to reproduce it).

Found as well a Redhat bugreport concerning this: https://bugzilla.redhat.com/show_bug.cgi?id=249435

coolo, please have a look at this.

*** Bug 327489 has been marked as a duplicate of this bug. ***

*** Bug 327420 has been marked as a duplicate of this bug. ***

I'm pretty sure it's a different symtom of the same bug

*** This bug has been marked as a duplicate of bug 326478 ***

Created attachment 175630 [details]
log.tgz

I have installed RC1 on a PC. After reboot the yast says nothing, apears olny text screen with login - but without password/user configurations steps I was not able log in to the system. So the attachment is the install raw log.