Bug 1128945

Summary:	Segmentation Fault in zypper on after upgrade to Tumbleweed 20190310
Product:	[openSUSE] openSUSE Tumbleweed	Reporter:	mekenok hearscrow <turtlevt>
Component:	Upgrade Problems	Assignee:	Michael Andres <ma>
Status:	RESOLVED DUPLICATE	QA Contact:	Jiri Srain <jsrain>
Severity:	Normal
Priority:	P5 - None	CC:	hattrick, nwr10cst-oslnx
Version:	Current
Target Milestone:	---
Hardware:	x86-64
OS:	SUSE Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description mekenok hearscrow 2019-03-12 16:03:04 UTC

Since upgrading to Tumbleweed 20190310, I have a segmentation fault in zypper.
If I restart zypper it continues from where the last fault occurred and segfaults again later. If I keep repeating the run, I eventually get everything in.

Entry from zypper logfile:

2019-03-12 11:21:34 <1> linux-5oyj(6530) [zypp] MediaCurl.cc(MediaCurl):577 MediaCurl::MediaCurl(http://suse.mobile-central.org/tumbleweed/repo/oss/x86_64/libsamba-hostconfig0-4.9.4+git.126.aa8e79e6e87-1.3.x86_64.rpm, )
2019-03-12 11:21:34 <1> linux-5oyj(6530) [zypp++] MediaCurl.cc(setupEasy):857 Proxy: not explicitly set
2019-03-12 11:21:34 <1> linux-5oyj(6530) [zypp++] MediaCurl.cc(setupEasy):858 Proxy: libcurl may look into the environment
2019-03-12 11:21:34 <5> linux-5oyj(6530) [zypp] ZYppFactory.cc(sigsegvHandler):55 Error: signal 11
2019-03-12 11:21:34 <5> linux-5oyj(6530) [zypp] ZYppFactory.cc(sigsegvHandler):55 [hd]: (-3) /usr/lib64/libzypp.so.1709 : zypp::dumpBacktrace(std::ostream&)+0x39 [0x7f06280a9539]
2019-03-12 11:21:34 <5> linux-5oyj(6530) [zypp] ZYppFactory.cc(sigsegvHandler):55 [hd]: (-2) /usr/lib64/libzypp.so.1709 : +0x393c7b [0x7f0628064c7b]
2019-03-12 11:21:34 <5> linux-5oyj(6530) [zypp] ZYppFactory.cc(sigsegvHandler):55 [hd]: (-1) /lib64/libc.so.6 : +0x3be10 [0x7f062778ee10]
2019-03-12 11:21:34 <5> linux-5oyj(6530) [zypp] ZYppFactory.cc(sigsegvHandler):55 vvvvvvvvvv----------------------------------------
2019-03-12 11:21:34 <5> linux-5oyj(6530) [zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (0) /usr/lib64/libcurl.so.4 : +0x3a5e1 [0x7f06275165e1]
2019-03-12 11:21:34 <5> linux-5oyj(6530) [zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (1) /usr/lib64/libcurl.so.4 : +0x1c187 [0x7f06274f8187]
2019-03-12 11:21:34 <5> linux-5oyj(6530) [zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (2) /usr/lib64/libcurl.so.4 : +0x1c366 [0x7f06274f8366]
2019-03-12 11:21:34 <5> linux-5oyj(6530) [zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (3) /usr/lib64/libcurl.so.4 : +0x55c62 [0x7f0627531c62]
2019-03-12 11:21:34 <5> linux-5oyj(6530) [zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (4) /usr/lib64/libcurl.so.4 : +0x22dab [0x7f06274fedab]
2019-03-12 11:21:34 <5> linux-5oyj(6530) [zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (5) /usr/lib64/libcurl.so.4 : +0x26dfc [0x7f0627502dfc]
2019-03-12 11:21:34 <5> linux-5oyj(6530) [zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (6) /usr/lib64/libcurl.so.4 : +0x388f7 [0x7f06275148f7]
2019-03-12 11:21:34 <5> linux-5oyj(6530) [zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (7) /usr/lib64/libcurl.so.4 : curl_multi_perform+0x99 [0x7f0627515ca9]
2019-03-12 11:21:34 <5> linux-5oyj(6530) [zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (8) /usr/lib64/libzypp.so.1709 : zypp::media::multifetchrequest::run(std::vector<zypp::Url, std::allocator<zypp::Url> >&)+0x14d [0x7f0627e720bd]
2019-03-12 11:21:34 <5> linux-5oyj(6530) [zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (9) /usr/lib64/libzypp.so.1709 : zypp::media::MediaMultiCurl::multifetch(zypp::filesystem::Pathname const&, _IO_FILE*, std::vector<zypp::Url, std::allocator<zypp::Url> >*, zypp::call
back::SendReport<zypp::media::DownloadProgressReport>*, zypp::media::MediaBlockList*, long) const+0x4dc [0x7f0627e745ac]
2019-03-12 11:21:34 <5> linux-5oyj(6530) [zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (10) /usr/lib64/libzypp.so.1709 : zypp::media::MediaMultiCurl::doGetFileCopy(zy
pp::filesystem::Pathname const&, zypp::filesystem::Pathname const&, zypp::callback::SendReport<zypp::media::DownloadProgressReport>&, zypp::ByteCount const&, zypp::base::Flags<zypp::media::MediaCurl::RequestOption>) const+0xb45 [0x7f0627e75525]
2019-03-12 11:21:34 <5> linux-5oyj(6530) [zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (11) /usr/lib64/libzypp.so.1709 : zypp::media::MediaCurl::getFileCopy(zypp::filesystem::Pathname const&, zypp::filesystem::Pathname const&, zypp::ByteCount const&) const+0xa3 [0x7f0627e6c0b3]
2019-03-12 11:21:34 <5> linux-5oyj(6530) [zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (12) /usr/lib64/libzypp.so.1709 : zypp::media::MediaCurl::getFile(zypp::filesystem::Pathname const&, zypp::ByteCount const&) const+0x80 [0x7f0627e61af0]
2019-03-12 11:21:34 <5> linux-5oyj(6530) [zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (13) /usr/lib64/libzypp.so.1709 : zypp::media::MediaHandler::provideFile(zypp::filesystem::Pathname, zypp::ByteCount const&) const+0x5d [0x7f0627e41b3d]
2019-03-12 11:21:34 <5> linux-5oyj(6530) [zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (14) /usr/lib64/libzypp.so.1709 : zypp::media::MediaAccess::provideFile(zypp::filesystem::Pathname const&, zypp::ByteCount const&) const+0x99 [0x7f0627e3c7a9]
2019-03-12 11:21:34 <5> linux-5oyj(6530) [zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (15) /usr/lib64/libzypp.so.1709 : zypp::media::MediaManager::provideFile(unsigned int, zypp::filesystem::Pathname const&, zypp::ByteCount const&) const+0x73 [0x7f0627e7eaf3]
2019-03-12 11:21:34 <5> linux-5oyj(6530) [zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (16) /usr/lib64/libzypp.so.1709 : +0x2fd2d4 [0x7f0627fce2d4]
2019-03-12 11:21:34 <5> linux-5oyj(6530) [zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (17) /usr/lib64/libzypp.so.1709 : zypp::MediaSetAccess::provide(boost::function<void (unsigned int, zypp::filesystem::Pathname const&)>, zypp::OnMediaLocation const&, zypp::base::Flags<zypp::MediaSetAccess::ProvideFileOption>, zypp::filesystem::Pathname const&)+0x245 [0x7f0627fcc3a5]
2019-03-12 11:21:34 <5> linux-5oyj(6530) [zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (18) /usr/lib64/libzypp.so.1709 : zypp::MediaSetAccess::provideFile(zypp::OnMediaLocation const&, zypp::base::Flags<zypp::MediaSetAccess::ProvideFileOption>, zypp::filesystem::Pathname const&)+0x69 [0x7f0627fcc6e9]
2019-03-12 11:21:34 <5> linux-5oyj(6530) [zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (19) /usr/lib64/libzypp.so.1709 : zypp::Fetcher::Impl::provideToDest(zypp::MediaSetAccess&, zypp::filesystem::Pathname const&, boost::shared_ptr<zypp::FetcherJob> const&)+0x26b [0x7f0627fa23ab]
2019-03-12 11:21:34 <5> linux-5oyj(6530) [zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (20) /usr/lib64/libzypp.so.1709 : zypp::Fetcher::Impl::start(zypp::filesystem::Pathname const&, zypp::MediaSetAccess&, boost::function<bool (zypp::ProgressData const&)> const&)+0x2c9 [0x7f0627fa2b19]
2019-03-12 11:21:34 <5> linux-5oyj(6530) [zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (21) /usr/lib64/libzypp.so.1709 : zypp::Fetcher::start(zypp::filesystem::Pathname const&, zypp::MediaSetAccess&, boost::function<bool (zypp::ProgressData const&)> const&)+0x395 [0x7f0627fa3d05]
2019-03-12 11:21:34 <5> linux-5oyj(6530) [zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (22) /usr/lib64/libzypp.so.1709 : zypp::repo::RepoMediaAccess::provideFile(zypp::RepoInfo, zypp::OnMediaLocation const&, zypp::ProvideFilePolicy const&)+0xc23 [0x7f0627eca1b3]
2019-03-12 11:21:34 <5> linux-5oyj(6530) [zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (23) /usr/lib64/libzypp.so.1709 : +0x1f6614 [0x7f0627ec7614]
2019-03-12 11:21:34 <5> linux-5oyj(6530) [zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (24) /usr/lib64/libzypp.so.1709 : zypp::repo::RpmPackageProvider::doProvidePackage() const+0x1d1 [0x7f0627ebb5d1]
2019-03-12 11:21:34 <5> linux-5oyj(6530) [zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (25) /usr/lib64/libzypp.so.1709 : zypp::repo::PackageProviderImpl<zypp::Package>::providePackage() const+0x52c [0x7f0627ec594c]
2019-03-12 11:21:34 <5> linux-5oyj(6530) [zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (26) /usr/lib64/libzypp.so.1709 : zypp::repo::PackageProvider::providePackage() const+0x26 [0x7f0627eba616]
2019-03-12 11:21:34 <5> linux-5oyj(6530) [zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (27) /usr/lib64/libzypp.so.1709 : zypp::target::RepoProvidePackage::operator()(zypp::PoolItem const&, bool)+0x3ca [0x7f0627f1413a]
2019-03-12 11:21:34 <5> linux-5oyj(6530) [zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (28) /usr/lib64/libzypp.so.1709 : +0x257a90 [0x7f0627f28a90]
2019-03-12 11:21:34 <5> linux-5oyj(6530) [zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (29) /usr/lib64/libzypp.so.1709 : zypp::target::CommitPackageCacheReadAhead::get(zypp::PoolItem const&)+0x206 [0x7f0627f16436]
2019-03-12 11:21:34 <5> linux-5oyj(6530) [zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (30) /usr/lib64/libzypp.so.1709 : zypp::target::CommitPackageCache::get(zypp::PoolItem const&)+0x5a [0x7f0627f1390a]
2019-03-12 11:21:34 <5> linux-5oyj(6530) [zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (31) /usr/lib64/libzypp.so.1709 : zypp::target::TargetImpl::commit(zypp::ResPool, zypp::ZYppCommitPolicy const&)+0x186e [0x7f0627f2776e]
2019-03-12 11:21:34 <5> linux-5oyj(6530) [zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (32) /usr/lib64/libzypp.so.1709 : zypp::zypp_detail::ZYppImpl::commit(zypp::ZYppCommitPolicy const&)+0x29f [0x7f0628069cef]
2019-03-12 11:21:34 <5> linux-5oyj(6530) [zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (33) /usr/lib64/libzypp.so.1709 : zypp::ZYpp::commit(zypp::ZYppCommitPolicy const&)+0x25 [0x7f0628061585]
2019-03-12 11:21:34 <5> linux-5oyj(6530) [zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (34) zypper : solve_and_commit(Zypper&, Summary::_view_options, zypp::DownloadMode)+0xa7d [0x56271be5c93d]
2019-03-12 11:21:34 <5> linux-5oyj(6530) [zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (35) zypper : DistUpgradeCmd::execute(Zypper&, std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > const&)+0xd0 [0x56271bdc3b60]
2019-03-12 11:21:34 <5> linux-5oyj(6530) [zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (36) zypper : ZypperBaseCommand::run(Zypper&)+0x2e5 [0x56271bd49b55]
2019-03-12 11:21:34 <5> linux-5oyj(6530) [zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (37) zypper : Zypper::doCommand(int, char**, int)+0xfe0 [0x56271bcf4cc0]
2019-03-12 11:21:34 <5> linux-5oyj(6530) [zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (38) zypper : Zypper::main(int, char**)+0x49 [0x56271bcd0369]
2019-03-12 11:21:34 <5> linux-5oyj(6530) [zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (39) zypper : main+0x40c [0x56271bccfcec]
2019-03-12 11:21:34 <5> linux-5oyj(6530) [zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (40) /lib64/libc.so.6 : __libc_start_main+0xeb [0x7f0627779b7b]
2019-03-12 11:21:34 <5> linux-5oyj(6530) [zypp] ZYppFactory.cc(sigsegvHandler):55 [bt]: (41) zypper : _start+0x2a [0x56271bcd251a]

Comment 1 Neil Rickert 2019-03-13 04:04:47 UTC

I can confirm this.

For me, it occurred during the update to 20190307.  There were 4 segfaults during that update.  The segfault occurs while downloading, and restarting "zypper" resumes where it left off.

There is a forum thread on this:
 https://forums.opensuse.org/showthread.php/535230-zypper-segfaulting

The best guess is that this is a "curl" bug.  Since "curl" was updated during the 20190310 update, it is possible that it has already been fixed.

Comment 2 Zurab Davitiani 2019-03-14 16:00:32 UTC

Seems like a dupe of bug 1127849. It seems like the most recent curl update indeed fixes it.

Comment 3 Neil Rickert 2019-03-17 17:16:32 UTC

Marking as duplicate of bug 1127849

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