Bugzilla – Bug 148577
software management and system update do not start after upgrade from SL10.1 (beta2) to SL10.1 (beta3)
Last modified: 2006-02-09 11:08:40 UTC
I upgraded from SL10.1 (beta2) to SL10.1 (beta3) using pub/opensuse/distribution/SL-OSS-factory/inst-source/suse/i586 "Software management" and "system update" no longer start, but other modules (e.g., YOU, Installation) still work. I will attach the y2log files in the next message.
Created attachment 66647 [details] /var/log/YaST2/y2log with examples of failed attempts I have provided one example each of attempts to start "Software Management" and "System Update"
Seth: What happens if you try to start these modules from the shell with `yast2 sw_single' or `yast2 update'?
You need to install yast2-ncurses to use the YaST2 text mode interface (-: sudo yast2 sw_single Error loading language plugin /usr/lib/YaST2/plugin/libpy2lang_perl.so: libperl.so: cannot open shared object file: No such file or directory No such client module sw_single sudo yast2 update Error loading language plugin /usr/lib/YaST2/plugin/libpy2lang_perl.so: libperl.so: cannot open shared object file: No such file or directory No such client module update
Are you sure these modules are installed? You have to install the packages yast2-packager and yast2-online-update.
Yes, I am sure these modules are installed. I was able to use Software Management and System Update with SL10.1 beta2 without problem. The problem appeared only after I upgraded to the versions from beta3 and last night I installed the version of yast2-packager from beta4 that is found on /pub/opensuse/distribution/SL-OSS-factory/inst-source/suse/i586, but the problem still appears, or more precisely, both System Update (and Software Management) do not start (i.e., do not appear) Note that Online Update has always worked without problem (i.e., it starts up, it is possible to make updates), as has Installation (where it is possible to specify the location of the source files).
Here is more precise information: > rpm -q yast2 yast2-2.13.26-2 ~> rpm -q yast2-packager yast2-packager-2.13.19-2 ~> rpm -q yast2-update yast2-update-2.13.0-2 > rpm -q yast2-online-update yast2-online-update-2.13.2-2 I think the problem is connected with yast2-perl-bindings, which owns /usr/lib/YaST2/plugin/libpy2lang_perl.so and refers to libperl.so which is owned by perl 5.8.8, which gets upgraded from perl 5.8.7 in going from beta2 to beta3. (See error message in comment #3 here) The latest verion (beta4) of yast2-perl-bindings is yast2-perl-bindings-2.13.4-2 I installed that. Now I can get a new (undertandable) error message. sudo yast2 update Error loading language plugin /usr/lib/YaST2/plugin/libpy2lang_perl.so: libzypp.so.0: cannot open shared object file: No such file or directory No such client module update because: rpm -V yast2-perl-bindings Unsatisfied dependencies for yast2-perl-bindings-2.13.4-2.i586: libzypp.so.0 I am guessing/hoping that if I could get this libzypp library, then the problem would disappear. I could not see anything in /pub/opensuse/distribution/SL-OSS-factory/inst-source/suse/i586 that might be relevant. (without Software Management, it is hard to search for "provides").
OK, this is most likely the fontconfig bug - again. Please install the updated packages you can find here: http://download.opensuse.org/distribution/SL-10.1-OSS-beta3/fixed-rpms Also: delete ~./font.cache-* (in all user's homedirs). After this it should work. If not, please reopen this bug. Sorry I didn't realize this earlier, but this bug has quite a number of sympthoms ;)