Bug 251121

Created attachment 122224 [details]
/var/log/YaST2/y2log

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1219033392 (LWP 5529)]
0xb6ff63ce in zypp::media::MediaManager_Impl::nextAccessId ()
   from /usr/lib/libzypp.so.300.0.0
(gdb) bt
#0  0xb6ff63ce in zypp::media::MediaManager_Impl::nextAccessId ()
   from /usr/lib/libzypp.so.300.0.0
#1  0xb6ff6059 in zypp::media::MediaManager::open ()
   from /usr/lib/libzypp.so.300.0.0
#2  0xb71acf6d in zypp::SourceFactory::createFrom ()
   from /usr/lib/libzypp.so.300.0.0
#3  0xb71ba8be in zypp::SourceManager::restore ()
   from /usr/lib/libzypp.so.300.0.0
#4  0xb5b868cd in PkgModuleFunctions::SourceRestore ()
   from /usr/lib/YaST2/plugin/libpy2Pkg.so.2
#5  0xb5b870e6 in PkgModuleFunctions::SourceStartManager ()
   from /usr/lib/YaST2/plugin/libpy2Pkg.so.2
#6  0xb5b3d4e5 in Y2PkgFunction::evaluateCall ()
   from /usr/lib/YaST2/plugin/libpy2Pkg.so.2
#7  0xb7d3bd43 in YEFunction::evaluate () from /usr/lib/libycp.so.3
#8  0xb7d4e726 in YSAssign::evaluate () from /usr/lib/libycp.so.3
#9  0xb7d6af88 in YBlock::evaluate () from /usr/lib/libycp.so.3
#10 0xb7d38e95 in Y2YCPFunction::evaluateCall () from /usr/lib/libycp.so.3
#11 0xb7d3bd43 in YEFunction::evaluate () from /usr/lib/libycp.so.3
#12 0xb7d4e726 in YSAssign::evaluate () from /usr/lib/libycp.so.3
#13 0xb7d6af88 in YBlock::evaluate () from /usr/lib/libycp.so.3
#14 0xb7d294b3 in YCPCodeRep::evaluate () from /usr/lib/libycp.so.3
#15 0xb7ef15d7 in Y2WFMComponent::doActualWork ()
---Type <return> to continue, or q <return> to quit---
   from /usr/lib/YaST2/plugin/libpy2wfm.so.2
#16 0xb7cc76c9 in main () from /usr/lib/liby2.so.2
#17 0xb7588e5c in __libc_start_main () from /lib/libc.so.6
#18 0x08048561 in main ()

Probably a duplicate of my own other report: Bug 251095

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

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

This morning there was another bunch of updates and it's working again now. (Information for other users who might have hit this bug: Of course you cannot use YaST to update itself if it crashes. Just use rpm or smart for that.)

So the issue is sort of resolved, but there's still a bug somewhere. One of the packages broke its ABI without specifying the dependencies correctly, or something like that.

"So the issue is sort of resolved, but there's still a bug somewhere. One of the
packages broke its ABI without specifying the dependencies correctly, or
something like that."

How can this issue be resolved, if you don't know what it was and assume there is still some issue lurking in the dark ?

Apart from that your "workaround" lacks information on what packages need to be updated manually with rpm / smart to get over it.

Andreas said that it's SORT of resolved. He then tells you that there is a solution, but don't want to close the bug.
You need to download and install libzypp-3.0.0-3.i586.rpm with rpm.

Thank you.

How about the part:

"GTK Accessibility Module initialized

** (gtk:4904): WARNING **: AT_SPI_REGISTRY was not started at session startup.

** (gtk:4904): WARNING **: IOR not set.

** (gtk:4904): WARNING **: Could not locate registry"

in your first report, is this a bug in it's own right ? I get this also when starting gedit or evolution from a terminal.

ARGH!

This is a pure gtk2 problem which has nothing to do with YaST, it might be caused by the fact that factory is currently half GNOME 2.18 and half still GNOME 2.16.

So it is a bug in it's own right, as i assumed from getting it with evolution and gedit as well. I think it should be reported and followed up as such, so it doesn't get left out.

fixed with latest libzypp.