Bug 106013

Summary: Segfault during instalation
Product: [openSUSE] SUSE LINUX 10.0 Reporter: Forgotten User 7L3tOtZIov <forgotten_7L3tOtZIov>
Component: InstallationAssignee: E-mail List <yast2-maintainers>
Status: RESOLVED WORKSFORME QA Contact: Klaus Kämpf <kkaempf>
Severity: Major    
Priority: P5 - None    
Version: Beta 2   
Target Milestone: ---   
Hardware: i686   
OS: All   
Whiteboard:
Found By: Beta-Customer Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: hwinfo on SUSE 9.1

Description Forgotten User 7L3tOtZIov 2005-08-20 16:17:07 UTC
When I boot I get a segmentationfault. I

t happens as well when I do the safe or without
ACPI instalation.

This is the errormessage I get:

integrating the shared objects of the instalation system...
starting syslog (messages are logged tp /dev/tty4)...
startingklogd ...
integrating kernel modules of the installation system...
starting yast...
/sbin/yast: line 243: test: -gt: unary operator expected
/usr/lib/YaST2/bin/YaST2: line 499:  3087 Done          cat /etc/X11/XF86Config
        3080 Segmentation fault | /usr/X11R6/bin/xupdate >/etc/X11/XF86Config.new
/usr/lib/YaST2/bin/YaST2: line 499:  3094 Segmentation fault    sleep1
/usr/lib/YaST2/bin/YaST2: line 499:  3104 Segmentation fault    sleep1
/usr/lib/YaST2/bin/YaST2: line 525:  3155 Segmentation fault    y2base
"modulename" '("nox11")' $moduleargs ncurses

No yast2 log available.
No problems with Beta 1.
Comment 1 Arvin Schnell 2005-08-22 08:54:43 UTC
Please descript the hardware as detailed as possible.  The output
of hwinfo of Beta 1 would certainly help.  Unless we find a system
here where we can reproduce this problem I see no chance in fixing
it.

Since this affects only certain hardware it's not a blocker.
Comment 2 Forgotten User 7L3tOtZIov 2005-08-22 09:16:23 UTC
Created attachment 46842 [details]
hwinfo on SUSE 9.1

Instalation with the boot.iso worked without any problem
Comment 3 Arvin Schnell 2005-08-25 08:52:55 UTC
We have not been able to reproduce the problem here.  Unfortunately this
means that we can't fix it, sorry.