Bugzilla – Bug 305236
Adding a third-party repository causes software installer to crash
Last modified: 2007-08-29 12:42:19 UTC
Created attachment 160226 [details] The Yast2 log files. Adding the Guru third party repository to a fresh beta 2 installation, causes both the Software Manager and Online Update modules to crash during loading. The following error message appears in the xmeesage panel that pops up: YaST got signal 11 at YCP file /usr/share/YaST2/clients/sw_single.ycp:187 /sbin/yast2: line 385: 4375 Segmentation fault $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2QT_ARGS Yast logs are attached.
If that repository is removed from the list, the installer does not crash.
It's an empty repo, but indeed it shouldn't crash.
Reproduced with zypper 0.8.16: #0 0x083a65c5 in ?? () #1 0x0938dfc0 in ?? () #2 0x08124270 in ?? () #3 0xbff07408 in ?? () #4 0xbff073bc in ?? () #5 0xb7f57ff4 in ?? () from /usr/lib/libzypp.so.313.5.4 #6 0x0a1a5270 in ?? () #7 0x083a65c0 in ?? () #8 0xbff073e8 in ?? () #9 0xb7b0589d in zypp::RWCOW_pointer<zypp::ProgressData::Data, zypp::rw_pointer::Shared<zypp::ProgressData::Data> >::assertUnshared () from /usr/lib/libzypp.so.313.5.4 #10 0xb7e01ef4 in zypp::CombinedProgressData::operator() () from /usr/lib/libzypp.so.313.5.4 #11 0xb7b348b4 in boost::detail::function::function_obj_invoker1<zypp::CombinedProgressData, bool, zypp::ProgressData const&>::invoke () from /usr/lib/libzypp.so.313.5.4 #12 0xb7e020d7 in boost::function1<bool, zypp::ProgressData const&, std::allocator<void> >::operator() () from /usr/lib/libzypp.so.313.5.4 #13 0xb7e0151e in zypp::ProgressData::report () from /usr/lib/libzypp.so.313.5.4 #14 0xb7c36c3f in zypp::repo::cached::RepoImpl::~RepoImpl () from /usr/lib/libzypp.so.313.5.4 #15 0xb7c17280 in zypp::repo::intrusive_ptr_release () from /usr/lib/libzypp.so.313.5.4 #16 0x080a020d in load_repo_resolvables () #17 0x080a9eb6 in cond_load_resolvables () #18 0x0807355e in one_command () #19 0x080753e1 in safe_one_command () #20 0x0807786a in main ()
*** This bug has been marked as a duplicate of bug 299680 ***