Slowroll yast error

GJElde · January 9, 2025, 11:15am

After yesterday’s Slowroll update I can’t open anything in Yast anymore.


2025-01-09 11:49:45 <3> vbox(2600) [Ruby] yast/wfm.rb(handle_exception):308 Internal error. Please report a bug report with logs.<br>Run save_y2logs to get complete logs.<br><br>Caller:  &lt;internal:/usr/lib64/ruby/3.3.0/rubygems/core_ext/kernel_require.rb&gt;:136:in `require&#39;<br><br>Details: Failed to load Module &#39;PackageSlideShow&#39; due to: Failed to load Module &#39;Packages&#39; due to: cannot load such file -- solv
2025-01-09 11:49:45 <1> vbox(2600) [ui] YPushButton.cc(setRole):170 Guessing function key F10 for YPushButton "OK" at 0x7f1a48004f80 from button role YOKButton
2025-01-09 11:49:45 <1> vbox(2600) [ui] YCPDialogParser.cc(parseButtonBox):1171 Relaxed sanity check for YButtonBox at 0x7f1a48004d90
2025-01-09 11:50:21 <1> vbox(2600) [Interpreter] bin/y2start:68 Called YaST client returned.
2025-01-09 11:50:21 <1> vbox(2600) [ncurses] YNCursesUI.cc(~YNCursesUI):126 Stop YNCursesUI
2025-01-09 11:50:21 <1> vbox(2600) [ncurses] NCurses.cc(~NCurses):145 Shutdown NCurses...
2025-01-09 11:50:21 <1> vbox(2600) [ncurses] NCurses.cc(~NCurses):164 NCurses down
2025-01-09 11:50:21 <1> vbox(2600) [Y2Ruby] binary/YRuby.cc(~YRuby):117 Shutting down ruby interpreter.
2025-01-09 11:50:22 <3> vbox(2309) [ncurses] NCApplication.cc(runInTerminal):215 /sbin/yast sw_single  >&2 returned:4096
2025-01-09 11:50:22 <1> vbox(2309) [ncurses] NCurses.cc(RedirectToLog):565 isatty(stderr)no
2025-01-09 11:50:22 <1> vbox(2309) [ncurses] NCurses.cc(RedirectToLog):574 isatty(stdout)no
2025-01-09 11:50:22 <1> vbox(2309) [Ruby] clients/menu.rb(Launch):314 Got 4096 from /sbin/yast sw_single  >&2
2025-01-09 11:50:22 <1> vbox(2309) [Interpreter] bin/y2start:68 Called YaST client returned.
2025-01-09 11:50:22 <1> vbox(2309) [ncurses] YNCursesUI.cc(~YNCursesUI):126 Stop YNCursesUI
2025-01-09 11:50:22 <1> vbox(2309) [ncurses] NCurses.cc(~NCurses):145 Shutdown NCurses...
2025-01-09 11:50:22 <1> vbox(2309) [ncurses] NCurses.cc(~NCurses):164 NCurses down
2025-01-09 11:50:22 <1> vbox(2309) [Y2Ruby] binary/YRuby.cc(~YRuby):117 Shutting down ruby interpreter.
2025-01-09 11:54:29 <1> vbox(3557) [Ruby] bin/y2start(<main>):22 y2base called with ["lan", "qt", "-name", "YaST2", "-icon", "yast"]
2025-01-09 11:54:29 <1> vbox(3557) [ui-component] YUIComponentCreator.cc(createInternal):124 Creating UI component for ""
2025-01-09 11:54:29 <1> vbox(3557) [ui] YUI.cc(YUI):83 This is libyui 4.6.3
2025-01-09 11:54:29 <1> vbox(3557) [ui] YUI.cc(YUI):84 Creating UI with threads
2025-01-09 11:54:29 <1> vbox(3557) [qt-ui] YQUI.cc(YQUI):110 This is libyui-qt 4.6.3
2025-01-09 11:54:29 <2> vbox(3557) [qt-ui] YQUI.cc(qMessageHandler):656 <libqt-warning> QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
2025-01-09 11:54:30 <1> vbox(3557) [qt-styler] QY2Styler.cc(loadStyleSheet):158 Using style sheet "/usr/share/YaST2/theme/current/wizard/style.qss"
2025-01-09 11:54:30 <1> vbox(3557) [qt-ui] YQUI.cc(processCommandLineArgs):259 Qt argument: /usr/bin/ruby.ruby3.3
2025-01-09 11:54:30 <1> vbox(3557) [qt-ui] YQUI.cc(processCommandLineArgs):259 Qt argument: --encoding=utf-8
2025-01-09 11:54:30 <1> vbox(3557) [qt-ui] YQUI.cc(processCommandLineArgs):259 Qt argument: /usr/lib/YaST2/bin/y2start
2025-01-09 11:54:30 <1> vbox(3557) [qt-ui] YQUI.cc(processCommandLineArgs):259 Qt argument: lan
2025-01-09 11:54:30 <1> vbox(3557) [qt-ui] YQUI.cc(processCommandLineArgs):259 Qt argument: qt
2025-01-09 11:54:30 <1> vbox(3557) [qt-ui] YQUI.cc(calcDefaultSize):412 Default size: 1176 x 628
2025-01-09 11:54:30 <1> vbox(3557) [qt-ui] YQApplication.cc(YQApplication):98 QIcon::themeName = 'breeze'
2025-01-09 11:54:30 <1> vbox(3557) [qt-ui] YQApplication.cc(loadPredefinedQtTranslations):153 Selected language: nl_NL
2025-01-09 11:54:30 <1> vbox(3557) [qt-ui] YQApplication.cc(loadPredefinedQtTranslations):173 Loaded translations for predefined Qt dialogs for nl_NL
2025-01-09 11:54:30 <1> vbox(3557) [qt-ui] YQUI.cc(initUI):236 YQUI initialized. Thread ID: 0x0x7fa7acd4f6c0
2025-01-09 11:54:30 <1> vbox(3557) [ui] YCP_UI.cc(SetApplicationTitle):1742 Setting application title to '"YaST2 - lan @ vbox                                                            "'
2025-01-09 11:54:31 <1> vbox(3557) [Interpreter] bin/y2start:68 Calling YaST client lan
2025-01-09 11:54:31 <1> vbox(3557) [Ruby] yast/wfm.rb(run_client):341 Call client /usr/share/YaST2/clients/lan.rb
2025-01-09 11:54:31 <1> vbox(3557) [Ruby] clients/lan.rb(main):41 ----------------------------------------
2025-01-09 11:54:31 <1> vbox(3557) [Ruby] clients/lan.rb(main):42 Lan module started
2025-01-09 11:54:31 <3> vbox(3557) [Y2Ruby] binary/Y2RubyUtils.cc(y2_require):26 cannot require yast:cannot load such file -- storage at <internal:/usr/lib64/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:136:in `require'
2025-01-09 11:54:31 <3> vbox(3557) [Y2Ruby] binary/Y2RubyComponent.cc(import):99 Reporting runtime error for import of module 'Lan' message 'cannot load such file -- storage'
2025-01-09 11:54:31 <3> vbox(3557) [Interpreter] yast/i18n.rb:169 Runtime error when loading module 'Lan'
2025-01-09 11:54:31 <3> vbox(3557) [Ruby] yast/wfm.rb(handle_exception):271 Client /usr/share/YaST2/clients/lan.rb failed with 'Failed to load Module 'Lan' due to: cannot load such file -- storage' (RuntimeError).
Backtrace:
<internal:/usr/lib64/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:136:in `require'
<internal:/usr/lib64/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:136:in `require'
/usr/share/YaST2/lib/y2storage/storage_enum_wrapper.rb:20:in `<top (required)>'
<internal:/usr/lib64/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:136:in `require'
<internal:/usr/lib64/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:136:in `require'
/usr/share/YaST2/lib/y2storage/view.rb:20:in `<top (required)>'
<internal:/usr/lib64/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:136:in `require'
<internal:/usr/lib64/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:136:in `require'
/usr/share/YaST2/lib/y2storage.rb:20:in `<top (required)>'
<internal:/usr/lib64/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:136:in `require'
<internal:/usr/lib64/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:136:in `require'
/usr/share/YaST2/lib/y2network/connection_config/base.rb:21:in `<top (required)>'
<internal:/usr/lib64/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:136:in `require'
<internal:/usr/lib64/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:136:in `require'
/usr/share/YaST2/lib/y2network/connection_config.rb:20:in `<top (required)>'
<internal:/usr/lib64/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:136:in `require'
<internal:/usr/lib64/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:136:in `require'
/usr/share/YaST2/lib/y2network/autoinst/s390_devices_reader.rb:22:in `<top (required)>'
<internal:/usr/lib64/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:136:in `require'
<internal:/usr/lib64/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:136:in `require'
/usr/share/YaST2/lib/network/network_autoyast.rb:22:in `<top (required)>'
<internal:/usr/lib64/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:136:in `require'
<internal:/usr/lib64/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:136:in `require'
/usr/share/YaST2/modules/Lan.rb:32:in `<top (required)>'
/usr/lib64/ruby/vendor_ruby/3.3.0/yast/yast.rb:186:in `import_pure'
/usr/lib64/ruby/vendor_ruby/3.3.0/yast/yast.rb:186:in `import'
/usr/share/YaST2/clients/lan.rb:46:in `main'
/usr/share/YaST2/clients/lan.rb:221:in `<top (required)>'
/usr/lib64/ruby/vendor_ruby/3.3.0/yast/wfm.rb:345:in `eval'
/usr/lib64/ruby/vendor_ruby/3.3.0/yast/wfm.rb:345:in `run_client'
/usr/lib64/ruby/vendor_ruby/3.3.0/yast/wfm.rb:206:in `call_builtin'
/usr/lib64/ruby/vendor_ruby/3.3.0/yast/wfm.rb:206:in `call_builtin_wrapper'
/usr/lib64/ruby/vendor_ruby/3.3.0/yast/wfm.rb:195:in `CallFunction'
/usr/lib/YaST2/bin/y2start:68:in `<main>'
2025-01-09 11:54:31 <3> vbox(3557) [Ruby] yast/wfm.rb(handle_exception):308 Internal error. Please report a bug report with logs.<br>Run save_y2logs to get complete logs.<br><br>Caller:  &lt;internal:/usr/lib64/ruby/3.3.0/rubygems/core_ext/kernel_require.rb&gt;:136:in `require&#39;<br><br>Details: Failed to load Module &#39;Lan&#39; due to: cannot load such file -- storage
2025-01-09 11:54:31 <1> vbox(3557) [ui] YPushButton.cc(setRole):170 Guessing function key F10 for YPushButton "OK" at 0x7fa7a81d4ee0 from button role YOKButton
2025-01-09 11:54:31 <1> vbox(3557) [ui] YCPDialogParser.cc(parseButtonBox):1171 Relaxed sanity check for YButtonBox at 0x7fa7a836efa0
2025-01-09 12:00:47 <1> vbox(3557) [Interpreter] bin/y2start:68 Called YaST client returned.
2025-01-09 12:00:47 <1> vbox(3557) [qt-ui] YQUI.cc(uiThreadDestructor):320 Destroying UI thread
2025-01-09 12:00:47 <1> vbox(3557) [qt-ui] YQUI.cc(~YQUI):302 Closing down Qt UI.
2025-01-09 12:00:47 <1> vbox(3557) [Y2Ruby] binary/YRuby.cc(~YRuby):117 Shutting down ruby interpreter.

Kelvino9 · January 9, 2025, 12:05pm

Same issue here after yesterday’s January version bump.

Brunhylde · January 9, 2025, 12:19pm

Hi,

I guess, same problem for me, after performing a system update on my Slowroll system, I encountered an issue where YaST’s package and repository management would not work. The error message displayed was:

Internal error. Please report a bug report with logs.
Failed to load Module ‘PackageSlideShow’ due to: Failed to load Module ‘Packages’ due to: cannot load such file – solv.

It’s seems that the problem was caused by missing Ruby modules, specifically solv.so and storage.so. These files were located in /usr/lib64/ruby/vendor_ruby/3.3.0/x86_64-linux-gnu/ and were absent after the update.

To resolve the issue, I used Btrfs snapshots (via YaST’s snapshot management tool) to restore the missing files solv.so and storage.so to the appropriate directory. Once the files were restored, YaST functioned correctly again, and the error was no longer present.

I hope this is usefull

arvidjaar · January 9, 2025, 12:37pm

How exactly did you update?

Package ruby-solv.

Package libstorage-ng-ruby.

Are these packages installed? Which versions?

Did anyone follow this advice?

Brunhylde · January 9, 2025, 12:48pm

With zypper refresh then zypper dup

sudo zypper se -si ruby-solv libstorage-ng-ruby
Chargement des données du dépôt...
Lecture des paquets installés...

S  | Name               | Type   | Version     | Arch   | Repository
---+--------------------+--------+-------------+--------+-------------------------------
i  | libstorage-ng-ruby | paquet | 4.5.221-1.2 | x86_64 | update-slowroll
i  | libstorage-ng-ruby | paquet | 4.5.221-1.2 | x86_64 | Dépôt principal de mise à jour
i  | ruby-solv          | paquet | 0.7.31-1.3  | x86_64 | update-slowroll
i  | ruby-solv          | paquet | 0.7.31-1.3  | x86_64 | Dépôt principal de mise à jour
e

Well, not me to be honnest.

GJElde · January 9, 2025, 12:57pm

I saw that solv.so and storage.so are in /usr/lib64/ruby/vendor_ruby/3.4.0/x86_64-linux-gnu/.
But that’s missing files from 3.3.0?

arvidjaar · January 9, 2025, 1:01pm

The current version in Tumbleweed is 0.7.31-1.2. Show

zypper search -sx ruby-solv libstorage-ng-ruby

Yes, Factory moved to Ruby 3.4, but it is not yet included in any Tumbleweed snapshot. Something went wrong in package selection for Slowroll.

Well, to fix bug it has to be reported.

GJElde · January 9, 2025, 1:06pm

vbox:~ # zypper se -si ruby-solv libstorage-ng-ruby
Loading repository data…
Reading installed packages…

Brunhylde · January 9, 2025, 1:09pm

sudo zypper search -sx ruby-solv libstorage-ng-ruby
[sudo] Mot de passe de root : 
Rafraichissement du service 'NVIDIA'.
Rafraichissement du service 'openSUSE'.
Chargement des données du dépôt...
Lecture des paquets installés...

S  | Name               | Type   | Version                    | Arch   | Repository
---+--------------------+--------+----------------------------+--------+-------------------------------
i  | libstorage-ng-ruby | paquet | 4.5.221-1.2                | x86_64 | update-slowroll
v  | libstorage-ng-ruby | paquet | 4.5.221-1.1                | x86_64 | update-slowroll
v  | libstorage-ng-ruby | paquet | 4.5.220-1.0.4.1.sr20241202 | x86_64 | update-slowroll
v  | libstorage-ng-ruby | paquet | 4.5.219-1.1                | x86_64 | update-slowroll
v  | libstorage-ng-ruby | paquet | 4.5.219-1.0.2.1.sr20241202 | x86_64 | update-slowroll
v  | libstorage-ng-ruby | paquet | 4.5.219-1.0.2.1.sr20240803 | x86_64 | update-slowroll
v  | libstorage-ng-ruby | paquet | 4.5.220-1.0.4.1.sr20241202 | i586   | update-slowroll
v  | libstorage-ng-ruby | paquet | 4.5.219-1.0.2.1.sr20241202 | i586   | update-slowroll
v  | libstorage-ng-ruby | paquet | 4.5.219-1.0.2.1.sr20240803 | i586   | update-slowroll
i  | libstorage-ng-ruby | paquet | 4.5.221-1.2                | x86_64 | Dépôt principal de mise à jour
v  | libstorage-ng-ruby | paquet | 4.5.221-1.1                | x86_64 | Dépôt principal de mise à jour
v  | libstorage-ng-ruby | paquet | 4.5.221-1.1                | x86_64 | repo-oss
v  | libstorage-ng-ruby | paquet | 4.5.220-1.0.4.1.sr20241202 | x86_64 | Dépôt principal de mise à jour
v  | libstorage-ng-ruby | paquet | 4.5.219-1.1                | x86_64 | Dépôt principal de mise à jour
v  | libstorage-ng-ruby | paquet | 4.5.219-1.0.2.1.sr20241202 | x86_64 | Dépôt principal de mise à jour
v  | libstorage-ng-ruby | paquet | 4.5.219-1.0.2.1.sr20240803 | x86_64 | Dépôt principal de mise à jour
v  | libstorage-ng-ruby | paquet | 4.5.220-1.0.4.1.sr20241202 | i586   | Dépôt principal de mise à jour
v  | libstorage-ng-ruby | paquet | 4.5.219-1.0.2.1.sr20241202 | i586   | Dépôt principal de mise à jour
v  | libstorage-ng-ruby | paquet | 4.5.219-1.0.2.1.sr20240803 | i586   | Dépôt principal de mise à jour
i  | ruby-solv          | paquet | 0.7.31-1.3                 | x86_64 | update-slowroll
v  | ruby-solv          | paquet | 0.7.31-1.2                 | x86_64 | update-slowroll
v  | ruby-solv          | paquet | 0.7.31-1.1.2.1.sr20241103  | x86_64 | update-slowroll
v  | ruby-solv          | paquet | 0.7.31-1.3                 | i586   | update-slowroll
v  | ruby-solv          | paquet | 0.7.31-1.2                 | i586   | update-slowroll
v  | ruby-solv          | paquet | 0.7.31-1.1.2.1.sr20241103  | i586   | update-slowroll
i  | ruby-solv          | paquet | 0.7.31-1.3                 | x86_64 | Dépôt principal de mise à jour
v  | ruby-solv          | paquet | 0.7.31-1.2                 | x86_64 | Dépôt principal de mise à jour
v  | ruby-solv          | paquet | 0.7.31-1.2                 | x86_64 | repo-oss
v  | ruby-solv          | paquet | 0.7.31-1.1.2.1.sr20241103  | x86_64 | Dépôt principal de mise à jour
v  | ruby-solv          | paquet | 0.7.31-1.3                 | i586   | Dépôt principal de mise à jour
v  | ruby-solv          | paquet | 0.7.31-1.2                 | i586   | Dépôt principal de mise à jour
v  | ruby-solv          | paquet | 0.7.31-1.1.2.1.sr20241103  | i586   | Dépôt principal de mise à jour

Sure, just I’m not familiar with bug report and I don’t know how to do it. I have to look at that and learn.

Anyway, thanks for helping.

arvidjaar · January 9, 2025, 1:14pm

Does downgrading to the older versions help?

zypper install --oldpackage libstorage-ng-ruby=4.5.221-1.1 ruby-solv=0.7.31-1.2

https://bugzilla.opensuse.org/, same user/password as here.

See also openSUSE:Submitting bug reports - openSUSE Wiki

Brunhylde · January 9, 2025, 1:23pm

Yes, it’s working.

Thanks for helping to bug report

arvidjaar · January 9, 2025, 1:26pm

You will need to lock these two packages until it is resolved, otherwise they may be updated again.

GJElde · January 9, 2025, 1:44pm

for me too, and the are locked

Thanks

Brunhylde · January 9, 2025, 4:05pm

Got it, thanks again !

Keyran17 · January 9, 2025, 7:46pm

Hi @arvidjaar
Thanks

arvidjaar · January 10, 2025, 7:29am

Should be fixed now according to Reddit - Dive into anything

Keyran17 · January 10, 2025, 9:47am

Hi @arvidjaar
After your intervention yast was working fine but 12 hours ago, stupidly, I updated restoring the bug. This morning the new zypper dup solved it!
Thanks again for your advice.

bmwiedemann · January 12, 2025, 7:19pm

I filed 1235598 – yast dependencies insufficient to improve packaging to avoid this failure in the future.

Make sure to remove the package-locks before the next version bump.

can · January 20, 2025, 3:00pm

Hi. I did a fresh install but I have the same problem. Is there a solution for this?