Mailinglist Archive: opensuse-bugs (4214 mails)

< Previous Next >
[Bug 722538] YaST2 package manager terminated with segmentation fault.

rens groenewegen <rens.groenewegen@xxxxxxxxx> changed:

What |Removed |Added
CC| |rens.groenewegen@xxxxxxxxx

--- Comment #10 from rens groenewegen <rens.groenewegen@xxxxxxxxx> 2012-01-12
22:25:34 UTC ---
got the same one, I think:

YaST got signal 11 at YCP file PackageInstallation.ycp:138
/sbin/yast2: line 427: 7200 Segmentation fault $ybindir/y2base $module

when repos are offline, (tested with iso file and directory) that is, not over
the internet,
everything is fine...

however, the yast2 software or repos is both broken in curses as well as gui
interface as soon as a network based repo is added or activated,

it is not only the software applet, it is also the repository applet:
after activating a web repos , as soon as one tries to do "refresh all
the repo interface crashes with the following:

YaST got signal 11 at YCP file /usr/share/YaST2/clients/repositories.ycp:1243
/sbin/yast2: line 427: 11567 Segmentation fault $ybindir/y2base $module

and the activation of the web based repo is forgotten or never happened.

however, if one activates a webbased repo and does NOT refresh, but simply
clicks ok, the change is accepted and activated.

consequently trying to use the software applet then results in a crash again,
with the interface showing the following message :

YaST got signal 11 at YCP file /usr/share/YaST2/clients/sw_single.ycp:307
/sbin/yast2: line 427: 12246 Segmentation fault $ybindir/y2base $module

removing the web based repo ( 12.1 OSS repository ) fixes this problem and
yast2 software is functional again, but without network based repositories.

please find the logs documenting the above sequence attached in the next

I noticed the yast2 packages, some of them are red. I assume because they are
the ones in the ISO repository, which are a older version then the ones
I also noticed that a 12.1 based appliance made with suse studio last night,
suffers from the same problem.....

hope this helps



Configure bugmail:
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >