autoyast - clone_system causes malloc () errors

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

Environment

SUSE Linux Enterprise Server 10 Service Pack 2

Situation

An autoyast system clone file (autoinst.xml), can be created with the graphical interface in YaST or directly invoking clone_system.ycp as follows:

host :~ # cd /usr/share/YaST2/clients/
host :/usr/share/YaST2/clients # /sbin/yast2 ./clone_system.ycp

Under certain circumstances on SUSE Linux Enterprise Server 10 SP2 it can trigger the following error:

host :/usr/share/YaST2/clients # /sbin/yast2 ./clone_system.ycp
terminate called after throwing an instance of 'std::bad_alloc'
  what():  St9bad_alloc
YaST got signal 6 at YCP file Printerdb.ycp:376
/sbin/yast2: line 276: 32182 Aborted                 $ybindir/y2base $module "$@" qt $Y2_GEOMETRY $Y2QT_ARGS



Or the command hangs when the second pop-up window informs the user that:
The list of installed drivers has changed. 
Building database of drivers....
In this case the command line error reports:
ffffffffff600000-ffffffffffe00000 ---p 00000000 00:00 0                  [vdso]
YaST got signal 6 at YCP file Printerdb.ycp:376

Resolution

The /sbin/yast2 ./clone_system.ycp command only fails when there is a missing driver in /usr/share/cups/model/*

A workaround is reinstalling cups-drivers and if needed, cups-drivers-stp. A pop-up window will inform the user that the database is rebuild and after informing the user that the system is collecting configuration data, the /root/autoinst.xml is created.

The problem is caused by a Bug in yast2-printer. The yast2-printer version  -2.13.34-0.4.20 in SUSE Linux Enterprise Server 10 SP3 corrects the problem.

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:7003938
  • Creation Date: 21-Jul-2009
  • Modified Date:24-Feb-2021
    • 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