Bugzilla – Bug 887051
yast2 sw_single segfaults
Last modified: 2014-08-19 18:57:29 UTC
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:30.0) Gecko/20100101 Firefox/30.0 yast2 sw_single segfaults all the time with openSUSE Factory. zypper 'up' and 'dup' both show no updates. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Please attach complete YaST2 logs which covers the issue. E.g. using save_y2logs as root.
Initially, I thought it was bug 866692 so I removed the libproxy1* packages. However, I still get this: 2014-07-18 20:52:22 <1> linux.site(13335) [zypp] ZYppFactory.cc(_openLockFile):166 Open lockfile /var/run/zypp.pid 2014-07-18 20:52:22 <1> linux.site(13335) [zypp] ZYppFactory.cc(~ZYppGlobalLock):115 Cleanned lock file. (13335) 2014-07-18 20:52:22 <1> linux.site(13335) [zypp] ZYppFactory.cc(_closeLockFile):184 Close lockfile /var/run/zypp.pid 2014-07-18 20:52:22 <1> linux.site(13335) [Pkg] PkgFunctions.cc(~PkgFunctions):150 Releasing the repo manager... 2014-07-18 20:52:22 <1> linux.site(13335) [Pkg] PkgFunctions.cc(~PkgFunctions):157 Releasing the zypp pointer... 2014-07-18 20:52:22 <5> linux.site(13335) [zypp] ZYppFactory.cc(sigsegvHandler):53 Error: signal 11 Which is not all that useful.
Does it also crash when using a different UI (e.g. textmode or Gtk)? Could you try running it as "yast sw_single" (in text mode)? Recently there was a bug fixed in Qt UI related to a crash at exit (bnc#879295, https://github.com/libyui/libyui-qt/pull/39). Which version of libyui-qt package do you have installed? It should be fixed in 2.46.12 and higher.
The crash does not happen in text mode. I cannot test gtk right now. i | libyui-qt-graph6 | package | 2.44.2-1.2 | x86_64 | openSUSE-20140626-1.2 i | libyui-qt-pkg6 | package | 2.44.5-1.3 | x86_64 | openSUSE-20140626-1.2 i | libyui-qt6 | package | 2.46.12-1.2 | x86_64 | openSUSE-20140626-1.2 'zypper ref' solves the problem for a while, but after ~10 minutes the segfault happens again. There is a thread in the opensuse forums where people claim that it depends on the Mesa version: http://forums.opensuse.org/showthread.php/498417-Testing-of-13-2-daily-snapshots/page5 Tarball of my /var/cache/zypp can be found in my Export, since it is too big for bugzilla. ~cwh/Export/yastlogs
I have reproduced the problem in openSUSE-13.1 + Yast from YaST:HEAD OBS, the backtrace is: #0 0x00007fffdc51b85e in ?? () from /usr/lib64/libkdecore.so.5 #1 0x00007ffff7deb85a in call_init.part.0 () from /lib64/ld-linux-x86-64.so.2 #2 0x00007ffff7deb943 in _dl_init_internal () from /lib64/ld-linux-x86-64.so.2 #3 0x00007ffff7defaa8 in dl_open_worker () from /lib64/ld-linux-x86-64.so.2 #4 0x00007ffff7deb6e4 in _dl_catch_error () from /lib64/ld-linux-x86-64.so.2 #5 0x00007ffff7def29b in _dl_open () from /lib64/ld-linux-x86-64.so.2 #6 0x00007ffff675802b in dlopen_doit () from /lib64/libdl.so.2 #7 0x00007ffff7deb6e4 in _dl_catch_error () from /lib64/ld-linux-x86-64.so.2 #8 0x00007ffff67585dd in _dlerror_run () from /lib64/libdl.so.2 #9 0x00007ffff67580c1 in dlopen@@GLIBC_2.2.5 () from /lib64/libdl.so.2 #10 0x00007fffefcdcf25 in libmodman::module_manager::load_file(std::string, bool) () from /usr/lib64/libmodman.so.1 #11 0x00007fffefcdd2b3 in libmodman::module_manager::load_dir(std::string, bool) () from /usr/lib64/libmodman.so.1 #12 0x00007ffff1b392b6 in ?? () from /usr/lib64/libproxy.so.1 #13 0x00007ffff1b39e8b in px_proxy_factory_new () from /usr/lib64/libproxy.so.1 #14 0x00007ffff3230681 in zypp::media::ProxyInfoLibproxy::ProxyInfoLibproxy() () from /usr/lib64/libzypp.so.1423 #15 0x00007ffff325a75c in zypp::media::ProxyInfo::ProxyInfo() () from /usr/lib64/libzypp.so.1423 #16 0x00007ffff325b8b2 in zypp::media::fillSettingsSystemProxy(zypp::Url const&, zypp::media::TransferSettings&) () from /usr/lib64/libzypp.so.1423 #17 0x00007ffff3263a33 in zypp::media::MediaCurl::setupEasy() () from /usr/lib64/libzypp.so.1423 After uninstalling libproxy1-config-kde4 it works for me. Christopher, could you try uninstalling the libproxy1-config-kde4 package to see if it helps?
Indeed, after uninstalling libproxy1-config-kde4 it works even without 'zypper ref'
OK, what we have seen is a duplicate of bnc#866692, however comment #2 says libproxy1* packages have been uninstalled. Jon, could you double check that libproxy1-config-kde4 is really not installed? Could you also check it text mode ("yast sw_single")?
BTW, bnc#866692 has been fixed by setting PX_MODULE_PATH="", could you try running yast with PX_MODULE_PATH="" yast2 sw_single command to see if it helps?
Created attachment 601778 [details] yast2 sw_single --gtk crash Possibly related to bug #891183 PX_MOD... has not effect. qt works fine.
Some more information, yast2 sw_single --gtk works once the system is installed, but fails as mentioned in comment #9 from live CD. To test boot up the GNOME_Next_testfixes.x86_64 iso from here: http://download.opensuse.org/repositories/GNOME:/Medias/images/iso/
yast2 sw_single no longer appears to segfault for me. I have libproxy1-config-kde4-0.4.11-10.8.x86_64 installed as well. I tried to simulate a refresh by using 'zypper clean --all' and then running 'yast2 sw_single' which worked fine (several times in a row). I am up-to-date as of Sun Aug 10 16:13:56 UTC 2014
Ok, so it seems that it was a duplicate of bnc#866692. *** This bug has been marked as a duplicate of bug 866692 ***