Yast segmentation fault on openSUSE 42.1

Hi all,

Problem: Yast2 seg faults when going to network module. To reproduce, launch yast2 in CLI and then select System > Network Settings. After the Initialization screen, it seems to be probing network settings and hardware, then returns back to the Yast2 menu. This happens whether using the stock openSUSE 42.1 distro, or after doing zypper update on the stock distro.

The error seems to have something to do with zypper, but I don't know how to fix this:

in /var/log/YaST2/y2log, I find this:

2016-07-02 04:06:30 <3> li759-229(3244) [Ruby] modules/Linuxrc.rb:55 Reading install.inf, but file doesn't exist!!!

2016-07-02 04:06:30 <5> li759-229(3244) [zypp] ZYppFactory.cc(sigsegvHandler):53 Error: signal 11

2016-07-02 04:06:30 <5> li759-229(3244) [zypp] ZYppFactory.cc(sigsegvHandler):53 [hd]: (-3) /usr/lib64/libzypp.so.1519 : zypp::dumpBacktrace

(std::ostream&)+0x26 [0x7f560121ace6]

2016-07-02 04:06:30 <5> li759-229(3244) [zypp] ZYppFactory.cc(sigsegvHandler):53 [hd]: (-2) /usr/lib64/libzypp.so.1519 : +0x32d40e [0x7f5601

1d640e]

2016-07-02 04:06:30 <5> li759-229(3244) [zypp] ZYppFactory.cc(sigsegvHandler):53 [hd]: (-1) /lib64/libc.so.6 : +0x35120 [0x7f5604968120]

2016-07-02 04:06:30 <5> li759-229(3244) [zypp] ZYppFactory.cc(sigsegvHandler):53 vvvvvvvvvv–--------------------------------------

2016-07-02 04:06:30 <5> li759-229(3244) [zypp] ZYppFactory.cc(sigsegvHandler):53 [bt]: (0) /usr/lib64/libruby2.1.so.2.1 : +0x18a332 [0x7f560

3e6e332]

2016-07-02 04:06:30 <5> li759-229(3244) [zypp] ZYppFactory.cc(sigsegvHandler):53 [bt]: (1) /usr/lib64/libruby2.1.so.2.1 : +0x6e953 [0x7f5603

d52953]

2016-07-02 04:06:30 <5> li759-229(3244) [zypp] ZYppFactory.cc(sigsegvHandler):53 [bt]: (2) /usr/lib64/libruby2.1.so.2.1 : rb_bug+0xb3 [0x7f5

603d52fc3]

2016-07-02 04:06:30 <5> li759-229(3244) [zypp] ZYppFactory.cc(sigsegvHandler):53 [bt]: (3) /usr/lib64/libruby2.1.so.2.1 : +0x121c86 [0x7f560

3e05c86

Please help!

1 Reply

Hmm, a bit awkward that I am answering my own question, but here goes: I found that you can choose to boot a different kernel, and booted to the 4.1.0 kernel version and yast worked like a charm after that. Probably some incompatibility between Yast and the 4.5.5 kernel.

Reply

Please enter an answer
Tips:

You can mention users to notify them: @username

You can use Markdown to format your question. For more examples see the Markdown Cheatsheet.

> I’m a blockquote.

I’m a blockquote.

[I'm a link] (https://www.google.com)

I'm a link

**I am bold** I am bold

*I am italicized* I am italicized

Community Code of Conduct