Bug 372989

Summary: y2base: segfault
Product: [openSUSE] openSUSE 11.0 Reporter: Casual J. Programmer <casualprogrammer>
Component: YaST2Assignee: E-mail List <yast2-maintainers>
Status: RESOLVED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Major    
Priority: P5 - None    
Version: Factory   
Target Milestone: ---   
Hardware: x86   
OS: openSUSE 11.0   
Whiteboard:
Found By: Beta-Customer Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: yast2 logs

Description Casual J. Programmer 2008-03-21 17:27:40 UTC 
After clean install from alpha3 DVD & update from factory, trying to oneclick install codecs-gnome.ymp from http://opensuse-community.org results in ( from cat /var/log/messages )

Mar 21 18:06:53 workstation6l klogd: y2base[14924]: segfault at 2d2d2d2d ip b7b0d4b6 sp b59acae0 error 4 in libgcc_s.so.1[b7b06000+c000]
Mar 21 18:08:44 workstation6l klogd: y2base[15179]: segfault at 5756695a ip b7a454b6 sp b58e4ae0 error 4 in libgcc_s.so.1[b7a3e000+c000]

after having been challenged with root password:

/sbin/yast2 OneClickInstallWorker /tmp/YaST2-1600

on entering root password an xmessage is displayed:

YaST got signal 11 at YCP file Wizard.ycp:273
/sbin/yast2: line 420: 16173 Segmentation fault      $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS

yast2-2.16.38-3
yast2-metapackage-handler-0.7.3-57
Comment 1 Casual J. Programmer 2008-03-21 17:28:47 UTC 
Created attachment 203433 [details]
yast2 logs
Comment 2 Stefan Hundhammer 2008-03-31 12:11:03 UTC 
This looks very much like bug #360646:

Perl-based YaST2 module crashes upon the first UI::OpenDialog() call.

2008-03-21 18:08:44 <1> workstation6l(15130) [YCP] PackageCallbacks.ycp:2469 Opening Wizard window...
2008-03-21 18:08:44 <1> workstation6l(15130) [YCP] SuSERelease.ycp:47 File with release information: /etc/SuSE-release
2008-03-21 18:08:44 <3> workstation6l(15130) [liby2] genericfrontend.cc(signal_handler):133 got signal 11 at YCP file Wizard.ycp:273


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