YaST2 error after slowroll update

English Applications
1

After a slowroll update today, I get the error message below when trying to open YaST2 or YaST. I have also liste the repositories I am using. The PC seems to work Ok other than I lost YaST. I have not tested it on CLI

Any suggestions?

Caller: <internal:/usr/lib64/ruby/3.4.0/rubygems/core_ext/kernel_require.rb>:136:in 'Kernel#require'

Details: Failed to load Module 'PackageSlideShow' due to: Failed to load Module 'Packages' due to: cannot load such file -- solv

zypper lr -d gives me:
 | Alias                    | Name            | Enabled | GPG Check | Refresh | Keep | Priority | Type   | URI                                                                          | Service
--+--------------------------+-----------------+---------+-----------+---------+------+----------+--------+------------------------------------------------------------------------------+---------
1 | NVIDIA:repo-non-free     | repo-non-free   | Yes     | (r ) Yes  | Yes     | -    |   99     | rpm-md | https://download.nvidia.com/opensuse/tumbleweed                              | NVIDIA
2 | openSUSE:repo-non-oss    | repo-non-oss    | Yes     | (r ) Yes  | Yes     | -    |   99     | rpm-md | http://download.opensuse.org/slowroll/repo/non-oss                           | openSUSE
3 | openSUSE:repo-openh264   | repo-openh264   | Yes     | (r ) Yes  | Yes     | -    |   99     | rpm-md | http://codecs.opensuse.org/openh264/openSUSE_Tumbleweed                      | openSUSE
4 | openSUSE:repo-oss        | repo-oss        | Yes     | (r ) Yes  | Yes     | -    |   99     | rpm-md | http://download.opensuse.org/slowroll/repo/oss                               | openSUSE
5 | openSUSE:repo-oss-debug  | repo-oss-debug  | No      | ----      | ----    | -    |   99     | N/A    | http://download.opensuse.org/debug/slowroll/repo/oss                         | openSUSE
6 | openSUSE:repo-oss-source | repo-oss-source | No      | ----      | ----    | -    |   99     | N/A    | http://download.opensuse.org/source/slowroll/repo/oss                        | openSUSE
7 | openSUSE:update-slowroll | update-slowroll | Yes     | (r ) Yes  | Yes     | -    |   80     | rpm-md | http://download.opensuse.org/update/slowroll/repo/oss                        | openSUSE
8 | packman                  | packman         | Yes     | (r ) Yes  | Yes     | -    |   70     | rpm-md | http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Slowroll/Essentials/ |
2

Show

rpm -q ruby ruby-solv
rpm -ql ruby-solv
3

Thank you @arvidjaar. Info below:

rpm -q ruby ruby-solv
ruby-3.4-1.1.x86_64
ruby-solv-0.7.31-1.2.x86_64

rpm -ql ruby-solv
/usr/lib64/ruby/vendor_ruby/3.3.0/x86_64-linux-gnu/solv.so
4

As you see, ruby-solv was built for Ruby 3.3.

Slowroll yast error - English / Install/Boot/Login - openSUSE Forums

@bmwiedemann ruby-solv needs update.

5

I tried to uninstall ruby-3.4 before installing ruby-3.3.0 but aborted as this would have removed 41 yast packages. Does it means I need to wait for a slowroll update of ruby-solv?

6

You can get updated package from Tumbleweed.

7

Sorry to come back - all my repositories are slowroll. Which tumbleweed repository should I add to get the update ruby-solv?

8 
rpm -U https://download.opensuse.org/tumbleweed/repo/oss/x86_64/ruby-solv-0.7.31-1.4.x86_64.rpm
9

@arvidjaar sorry to keep coming back. I updated ruby-solv as suggested, all ok but the same yast error keeps coming up. In y2logs I found a number of messages that make no sense to me but appear relevant. Do they give some clues?. If nor I will just let it be!

2025-02-12 21:54:34 <1> localhost.localdomain(19179) [Ruby] modules/Encoding.rb(Yast::EncodingClass#SetUtf8Lang):114 SetUtf8Lang true
2025-02-12 21:54:34 <3> localhost.localdomain(19179) [Y2Ruby] binary/Y2RubyUtils.cc(y2_require):26 cannot require yast:cannot load such file -- solv at <internal:/usr/lib64/ruby/3.4.0/rubygems/core_ext/kernel_require.rb>:136:in 'Kernel#require'
2025-02-12 21:54:34 <3> localhost.localdomain(19179) [Y2Ruby] binary/Y2RubyComponent.cc(import):99 Reporting runtime error for import of module 'Packages' message 'cannot load such file -- solv'
2025-02-12 21:54:34 <3> localhost.localdomain(19179) [Interpreter] yast/i18n.rb:169 Runtime error when loading module 'Packages'
2025-02-12 21:54:34 <3> localhost.localdomain(19179) [Y2Ruby] binary/Y2RubyUtils.cc(y2_require):26 cannot require yast:Failed to load Module 'Packages' due to: cannot load such file -- solv at <internal:/usr/lib64/ruby/3.4.0/rubygems/core_ext/kernel_require.rb>:136:in 'Kernel#require'
2025-02-12 21:54:34 <3> localhost.localdomain(19179) [Y2Ruby] binary/Y2RubyComponent.cc(import):99 Reporting runtime error for import of module 'PackageSlideShow' message 'Failed to load Module 'Packages' due to: cannot load such file -- solv'
2025-02-12 21:54:34 <3> localhost.localdomain(19179) [Interpreter] yast/i18n.rb:169 Runtime error when loading module 'PackageSlideShow'
2025-02-12 21:54:34 <3> localhost.localdomain(19179) [Ruby] yast/wfm.rb(Yast::WFM.handle_exception):271 Client /usr/share/YaST2/clients/sw_single.rb failed with 'Failed to load Module 'PackageSlideShow' due to: Failed to load Module 'Packages' due to: cannot load such file -- solv' (RuntimeError).
Backtrace:
<internal:/usr/lib64/ruby/3.4.0/rubygems/core_ext/kernel_require.rb>:136:in 'Kernel#require'
10

Show the same information as before.

11

These are the updated revisions I got after the update

rpm -q ruby ruby-solv
ruby-3.4-1.1.x86_64
ruby-solv-0.7.31-1.4.x86_64

rpm -ql ruby-solv
/usr/lib64/ruby/vendor_ruby/3.4.0/x86_64-linux-gnu/solv.so
12

Well, there could be some other outdated component. There is similar bug report: 1237133 – Error on opening software module after dup to new Slowroll update 20250212T2201

13

This was 1237133 – Error on opening software module after dup to new Slowroll update 20250212T2201 and is solved now. Just zypper dup

14

Thank you @arvidjaar and @ bmwiedemann. The last update included about 42 packages including kernel and something there resolved the problem. All now back to normal !

15

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.