Yast2 modules will not load in SLES

This document (7007717) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Desktop 10
SUSE Linux Enterprise Desktop 11
SUSE Linux Enterprise Server 10
SUSE Linux Enterprise Server 11

Situation

*one*

Yast2 modules start to load but then suddenly exit with no on screen errors.

Looking at /var/log/YaST2/y2log reveals the following perl errors.

Perl wanted to die: Can't locate YaPI/*******.pm in @INC

*Two*

ncurses modules works but the GUI does not.


Resolution

In some cases the problem has been associated with the “/root/.Xauthority” file. Some users have reported deleating the .Xauthority file and reopening yast failModule to fix the issue.


In the event that does not work follow these steps to troubleshoot.


1) First identify that you have the following issue by opening the failed module. For example: “yast2 users”.
2) Next check the /var/log/YaST2/y2log for errors shortly after the model loads. Below you will see an excerpt from the module users. Note the failure in this following example.


users/complex.ycp:274 Perl wanted to die: Can't locate YaPI/MailServer.pm in @INC

BEGIN failed--compilation aborted at /usr/share/YaST2/modules/UsersPluginMail.pm line 21.

Compilation failed in require at /usr/lib/perl5/vendor_perl/5.10.0/x86_64-linux-thread-multi/YaST/YCP.pm line 413.

BEGIN failed--compilation aborted.

clients/users.ycp:222 Users module finished with false



The module “users” failed because yast could not locate MailServer.pm “Can't locate YaPI/MailServer.pm

3) Locate the MailServer.pm with one of the following 2 methods on a working system. If no working system is present try looking for the missing Parent package by running

rpm -qa | grep yast2-users

rpm -q --provides yast2-users-2.17.28-1.52

In this example the the following  was returned:

package MailServer is not installed.

Otherwise on a working system locate the .pm by running:

llinux:/var/log/YaST2 # locate MailServer.pm

/usr/share/YaST2/modules/YaPI/MailServer.pm

or

find / -name “MailServer.pm”


4) In this test case the file did not exist on the failed server but did on a working one.

5) Verify what package owns “MailServer.pm” on the working system with:

rpm -qf /usr/share/YaST2/modules/YaPI/MailServer.pm

yast2-mail-x.x.x.x-x


6) Reinstalled the missing package. In this case it was yast2-mail. Run yast -i yast2-mail

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:7007717
  • Creation Date: 28-Jan-2011
  • Modified Date:03-Mar-2020
    • SUSE Linux Enterprise Desktop
    • SUSE Linux Enterprise Server

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback@suse.com

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

Join Our Community

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.


SUSE Customer Support Quick Reference Guide SUSE Technical Support Handbook Update Advisories
Support FAQ

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.

Go to Customer Center