Bug 410724 - YaST got signal 11 at YCP file /usr/share/YaST2/clients/inst_packages.ycp:49
Summary: YaST got signal 11 at YCP file /usr/share/YaST2/clients/inst_packages.ycp:49
Status: RESOLVED DUPLICATE of bug 399465
Alias: None
Product: openSUSE 11.0
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Final
Hardware: x86-64 Other
: P5 - None : Normal with 1 vote (vote)
Target Milestone: ---
Assignee: Michael Meeks
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-20 13:37 UTC by Nikita Manovich
Modified: 2008-07-23 12:38 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
logs of Yast2 (1.76 MB, application/x-gzip)
2008-07-21 18:52 UTC, Nikita Manovich
Details
hwinfo output (106.50 KB, application/x-gzip)
2008-07-21 18:58 UTC, Nikita Manovich
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Nikita Manovich 2008-07-20 13:37:25 UTC
1. I selected openastromenace-lang package. YaST added also openastromenace and openastromenace-data.
2. After that I seleted openastromenace package and in context menu I clicked on "undo".

Result:
xmessage dialog with the following message:
cat: write error: Broken pipe
YaST got signal 11 at YCP file /usr/share/YaST2/clients/inst_packages.ycp:49
/sbin/yast2: line 421: 16777 Segmentation fault   $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS

I can reproduce the problem regularly. 

Package:
nikman@linux-nikman:~> rpm -qi yast2-2.16.71-6.1
Name        : yast2                        Relocations: /usr 
Version     : 2.16.71                           Vendor: SUSE LINUX Products GmbH, Nuernberg, Germany
Release     : 6.1                           Build Date: Sat 07 Jun 2008 08:15:59 AM MSD
Install Date: Tue 10 Jun 2008 04:31:05 PM MSD      Build Host: cimarosa.suse.de
Group       : System/YaST                   Source RPM: yast2-2.16.71-6.1.src.rpm
Size        : 3206436                          License: GPL v2 or later
Signature   : DSA/SHA1, Sat 07 Jun 2008 08:18:07 AM MSD, Key ID a84edae89c800aca
Packager    : http://bugs.opensuse.org
Summary     : YaST2 - Main Package
Description :
This package contains scripts and data needed for SuSE Linux
installation with YaST2

nikman@linux-nikman:~> rpm -qi yast2-packager-2.16.53-3.1
Name        : yast2-packager               Relocations: /usr 
Version     : 2.16.53                           Vendor: SUSE LINUX Products GmbH, Nuernberg, Germany
Release     : 3.1                           Build Date: Sat 07 Jun 2008 08:58:55 AM MSD
Install Date: Tue 10 Jun 2008 04:32:09 PM MSD      Build Host: poincare.suse.de
Group       : System/YaST                   Source RPM: yast2-packager-2.16.53-3.1.src.rpm
Size        : 1611419                          License: GPL v2 or later
Signature   : DSA/SHA1, Sat 07 Jun 2008 09:00:39 AM MSD, Key ID a84edae89c800aca
Packager    : http://bugs.opensuse.org
Summary     : YaST2 - Package Library
Description :
This package contains the scanner/parser and dependency checker for all
packages handled by YaST2.



Authors:
--------
    Klaus Kaempf <kkaempf@suse.de>
    Stefan Schubert <schubi@suse.de>
    Arvin Schnell <arvin@suse.de>
Distribution: openSUSE 11.0 (X86-64)

nikman@linux-nikman:~> uname -a
Linux linux-nikman 2.6.25.9-0.2-default #1 SMP 2008-06-28 00:00:07 +0200 x86_64 x86_64 x86_64 GNU/Linux
Comment 1 Cyril Hrubis 2008-07-21 10:54:35 UTC
Please attach y2logs. If you are in doubt follow:

http://en.opensuse.org/Bugs/YaST

Thanks!
Comment 2 Nikita Manovich 2008-07-21 18:52:52 UTC
Created attachment 229161 [details]
logs of Yast2
Comment 3 Nikita Manovich 2008-07-21 18:58:15 UTC
Created attachment 229162 [details]
hwinfo output
Comment 4 Ladislav Slezák 2008-07-23 10:43:35 UTC
According to the backtrace the problem seems to be in the Gtk package selector.
Comment 5 Forgotten User h13THG8RK1 2008-07-23 12:38:03 UTC
It comes down to the following bug. There should be an update soon cause of bug 394309.

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