Bug 1129501

Summary: YaST2 - Software management crash
Product: [openSUSE] openSUSE Tumbleweed Reporter: Konrad Krzewinski <EtherealTouch>
Component: YaST2Assignee: E-mail List <yast2-maintainers>
Status: RESOLVED FIXED QA Contact: Jiri Srain <jsrain>
Severity: Major    
Priority: P5 - None CC: nwr10cst-oslnx
Version: Current   
Target Milestone: ---   
Hardware: x86-64   
OS: openSUSE Factory   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: y2logs

Description Konrad Krzewinski 2019-03-17 22:15:05 UTC
Created attachment 800300 [details]
y2logs

Hey folks,

I get an issue currently where, when I use YaST2's Software Management, it crashes shortly after it begins downloading packages. I think in particular, it fails at the moment that it attempts to install.

"
Caller: /usr/lib64/ruby/vendor_ruby/2.6.0/yast/yast.rb:204:in `call_yast_function'

Details: stack level too deep
"

Above is the initial output.

I've also attached the y2logs. Hope this helps.
Comment 1 Konrad Krzewinski 2019-03-17 22:20:23 UTC
Additional note: This seems to also extend to the ncurses version of yast. Wasn't able to install new applications there for some reason.
Comment 2 Konrad Krzewinski 2019-03-17 23:14:23 UTC
Pardon the spam- but one minor correction: This happens at random when attempting to install or update packages.

It can be while downloading. It can be when it's attempting to install.
Comment 3 Neil Rickert 2019-03-18 00:54:39 UTC
I'm not sure, but this may be the same problem as in bug 1127849

Most people who run into this see it with "zypper" rather than Yast.  The segfault occurs when downloading packages (or repo metadata), so I think that's what you are seeing.

It should be fixed if you are fully up-to-date.

Maybe run:  zypper update libcurl4
to fix the bug.

The correct way to update Tumbleweed is:

zypper dup

If you are updating with Yast, it is possible that you are not fully updated.  Maybe try
zypper dup
at a root terminal.  At least try a test run (you can add "--dry-run" to the end of the command), to see what changes it wants to make.
Comment 4 Konrad Krzewinski 2019-03-18 01:05:52 UTC
zypper update libcurl4

Fixed the issue.

I always update through Yast rather than Zypper. Basically the same thing minus a few differences, no? (I'm still learning, be gentle).
Comment 5 Neil Rickert 2019-03-18 01:50:19 UTC
I suggest you try:
zypper dup --dry-run

It won't actually change anything on your system, because of the "--dry-run".  It will just report the changes that it would make without that option.

It will give you an idea of how well your current update method is working.