RegataOS, based OpensuseLeap.15.1 YaST2 error, Ruby

[Gregor]

After a major update of Regata OS, the YaST2 software update and Zypper became unavailable in both the terminal and the GUI.

OS: Regata OS 24 Arctic Fox x86_64 Kernel: 6.7.7-lp155.10-default Packages: 3647 (rpm), 5 (flatpak), 14 (snap) Shell: bash 4.4.23 Terminal: console

Error messages:

sudo zypper update zypper: symbol lookup error: zypper: undefined symbol: _ZN4zypp5debug7MeasureC1ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE, version ZYPP_plain

On a graphical interface:

Internal error. Please report a bug report with logs. Run save_y2logs to get complete logs.

Caller: /usr/lib64/ruby/vendor_ruby/2.5.0/yast/yast.rb:186:in `import_pure’

Details: component cannot import namespace ‘Pkg’

VAR log:

024-03-16 00:48:05 <1> gr-pc(25162) [Ruby] bin/y2start():22 y2base called with [“sw_single”, “qt”, “-name”, “YaST2”, “-icon”, “yast”]
2024-03-16 00:48:05 <1> gr-pc(25162) [ui-component] YUIComponentCreator.cc(createInternal):124 Creating UI component for “”
2024-03-16 00:48:05 <1> gr-pc(25162) [ui] YUI.cc(YUI):83 This is libyui 4.5.2
2024-03-16 00:48:05 <1> gr-pc(25162) [ui] YUI.cc(YUI):84 Creating UI with threads
2024-03-16 00:48:05 <1> gr-pc(25162) [qt-ui] YQUI.cc(YQUI):110 This is libyui-qt 4.5.2
2024-03-16 00:48:05 <3> gr-pc(25162) [qt-ui] YQUI.cc(qMessageHandler):660 Failed to create wl_display (No such file or directory)
2024-03-16 00:48:05 <1> gr-pc(25162) [qt-ui] YQUI.cc(qMessageHandler):647 Could not load the Qt platform plugin “wayland” in “” even though it was found.
2024-03-16 00:48:05 <2> gr-pc(25162) [qt-ui] YQUI.cc(qMessageHandler):656 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to ‘/tmp/runtime-root’
2024-03-16 00:48:05 <1> gr-pc(25162) [qt-styler] QY2Styler.cc(loadStyleSheet):158 Using style sheet “/usr/share/YaST2/theme/current/wizard/style.qss”
2024-03-16 00:48:05 <1> gr-pc(25162) [qt-ui] YQUI.cc(processCommandLineArgs):259 Qt argument: /usr/bin/ruby.ruby2.5
2024-03-16 00:48:05 <1> gr-pc(25162) [qt-ui] YQUI.cc(processCommandLineArgs):259 Qt argument: --encoding=utf-8
2024-03-16 00:48:05 <1> gr-pc(25162) [qt-ui] YQUI.cc(processCommandLineArgs):259 Qt argument: /usr/lib/YaST2/bin/y2start
2024-03-16 00:48:05 <1> gr-pc(25162) [qt-ui] YQUI.cc(processCommandLineArgs):259 Qt argument: sw_single
2024-03-16 00:48:05 <1> gr-pc(25162) [qt-ui] YQUI.cc(processCommandLineArgs):259 Qt argument: qt
2024-03-16 00:48:05 <1> gr-pc(25162) [qt-ui] YQUI.cc(processCommandLineArgs):259 Qt argument: -icon
2024-03-16 00:48:05 <1> gr-pc(25162) [qt-ui] YQUI.cc(processCommandLineArgs):259 Qt argument: yast
2024-03-16 00:48:05 <1> gr-pc(25162) [qt-ui] YQUI.cc(calcDefaultSize):412 Default size: 1344 x 724
2024-03-16 00:48:05 <1> gr-pc(25162) [qt-ui] YQApplication.cc(YQApplication):98 QIcon::themeName = ‘breeze-dark’
2024-03-16 00:48:05 <1> gr-pc(25162) [qt-ui] YQApplication.cc(loadPredefinedQtTranslations):153 Selected language: hu_HU
2024-03-16 00:48:05 <1> gr-pc(25162) [qt-ui] YQApplication.cc(loadPredefinedQtTranslations):173 Loaded translations for predefined Qt dialogs for hu_HU
2024-03-16 00:48:05 <1> gr-pc(25162) [qt-ui] YQUI.cc(initUI):236 YQUI initialized. Thread ID: 0x0x7fe1870006c0
2024-03-16 00:48:05 <1> gr-pc(25162) [ui] YCP_UI.cc(SetApplicationTitle):1742 Setting application title to ‘"YaST2 - sw_single @ gr-pc >
2024-03-16 00:48:05 <1> gr-pc(25162) [Interpreter] bin/y2start:68 Calling YaST client sw_single
2024-03-16 00:48:05 <1> gr-pc(25162) [Ruby] yast/wfm.rb(run_client):341 Call client /usr/share/YaST2/clients/sw_single.rb
2024-03-16 00:48:05 <3> gr-pc(25162) [liby2] Y2PluginComponent.cc(loadPlugin):234 error loading plugin /usr/lib64/YaST2/plugin/libpy2Pkg.so.2: /usr/lib64/YaST2/plugin/lib>
2024-03-16 00:48:05 <3> gr-pc(25162) [liby2] Y2PluginComponent.cc(loadPlugin):234 error loading plugin /usr/lib64/YaST2/plugin/libpy2Pkg.so.2: /usr/lib64/YaST2/plugin/lib>
2024-03-16 00:48:05 <3> gr-pc(25162) [Interpreter] bin/y2start:68 Loading module ‘Pkg’ failed
2024-03-16 00:48:05 <3> gr-pc(25162) [libycp] Import.cc(import):97 No matching component found
2024-03-16 00:48:05 <3> gr-pc(25162) [Ruby] binary/Yast.cc(getNs):67 ruby call: Can’t import namespace ‘Pkg’
2024-03-16 00:48:05 <3> gr-pc(25162) [Ruby] yast/wfm.rb(handle_exception):271 Client /usr/share/YaST2/clients/sw_single.rb failed with ‘component cannot import namespace >
Backtrace:
/usr/lib64/ruby/vendor_ruby/2.5.0/yast/yast.rb:186:in import_pure' /usr/lib64/ruby/vendor_ruby/2.5.0/yast/yast.rb:186:in import’
/usr/share/YaST2/lib/y2packager/resolvable.rb:15:in <top (required)>' /usr/lib64/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in require’
/usr/lib64/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require’

Can anyone help me on how to fix it?

YaST2 is broken after executing zypper update

Unfortunately, no sudo zypper command in the terminal works.

[malcolmlewis]

@Gregor Hi and welcome to the Forum
This is a third party distribution, so you might be better off asking in their support channels.

[hui]

Also see this warning regarding use of RegataOS.

Regata OS warning

Due to inappropriate behavior of a new user, the thread regarding Regata OS had to be closed. Nevertheless, I took the trouble to take a closer look at this “operating system”. Here are a few reasons why this “operating system” is a very bad copy of openSUSE with major security issues and more. It is “maintained” by one guy. And “maintaining” means in this case, removing repos with security updates and adding countless not matching and untested repos. But see yourself… test@test-pc:~> cat /etc…

[Gregor]

Thanks for the reply!
I’ll see what can be done.

[Fraser_Bell]

What can be done is the removal of that OS, then install openSUSE from the official site.

[Gregor]

The solution was to download this package, extract it and copy the files to the system root (/), replacing the existing files.

This solution works. I like SUSE systems, YaST2 is very good. After Manjaro I wanted to try something different. This OS is not bad. In addition, they were even able to help on the forum.

Thank you for answering my question!

[pavinjoseph]

Thanks for coming back and specifying the solution

It appears to be a long-standing issue, zypper dup eating itself:

Zypper error while loading shared libraries

Happened recently too:
https://bugzilla.opensuse.org/show_bug.cgi?id=1219562

[hui]

@Gregor

I like SUSE systems, YaST2 is very good.

But why do you use a bad ripp-off like RegataOS then? If you want to have a maintained and secure operating system, you should use openSUSE and not one which disables all security meassures.

[hui]

A 12 year old thread with a different error message…

The actual bugreport describes a complete different mechanism which caused the actual issue from 2024.

[pavinjoseph]

Different symptoms, yes, but all leading back to the same problem. zypper dup breaks the update stack requiring some libraries like libzypp or librpm to be manually fetched and installed

[pavinjoseph]

@pavinjoseph

zypper dup breaks the update stack

The solution is to use transactional-update (TU):

The Transactional Update Guide

Run TU dup in interactive mode if zypper eats zypper. Then fix things as necessary from a working system/snapshot all without altering/breaking the currently running system/snapshot.

P.S. Sorry for the back to back reply, I’ve run out of time to edit the previous post.

[hui]

Please don‘t spread confusion by adding unrelated stuff. Transactional-update is mainly used for immutable distributions. Tumbleweed an Leap use zypper and snapshots. It is OK if you use it on your machine and break stuff. It is your machine. But don‘t recommend it and permanently advertise it for distributions where it is not intended for…

[pavinjoseph]

@hui

Transactional-update is mainly used for immutable distributions.

It was designed for both read-only and read-write root filesystems, probably keeping the ALP future in mind.

The only argument I’ve heard against it repeatedly on this forum is that’s not how we do it, so you shouldn’t too. As long as your argument is that, I think I will continue to recommend it when appropriate especially when not using TU results in a broken system.

[OrsoBruno]

@pavinjoseph

zypper dup breaks the update stack

No, zypper breaks nothing, manually aborting an upgrade when it is halfway through breaks things…

[pavinjoseph]

@OrsoBruno

No, zypper breaks nothing, manually aborting an upgrade when it is halfway through breaks things…

It’s more nuanced than that.
The default zypper action on error is to abort, so all non-interactive dup would naturally abort on error.
When choosing to ignore the error, you essentially end up with a broken/inconsistent system due to some package failing to install or as is more often the case some scripts associated with a package failing to do their job.

TU provides the tools to gracefully deal with both situations.

[malcolmlewis]

@pavinjoseph I suggest you refrain from pushing your transactional-update agenda on Forum users, simple solution, go blog about it somewhere. This forum thread is closed since in all essence it’s resolved for the user.

I’ll remind all that we are here to resolve user technical problems with their issues, with their setup whatever it maybe.