Zypper segfault related to syntax in /etc/sysconfig/proxy

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

Environment

SUSE Linux Enterprise Server 15 Service Pack 6

Situation

Some commands used with zypper result in a segfault error e.g.:

     # zypper ref
     Segmentation fault (core dumped)

Resolution

Either remove the trailing comma from the NO_PROXY statement variable in /etc/sysconfig/proxy file, or upgrade the libpxbackend-1_0 package to the version 0.5.3-150600.4.6.2 which contains patches to handle trailing commas and invalid proxy URIs.

Cause

The problem in this case was happening on a server with a configured proxy. The /etc/sysconfig/proxy file contained a trailing comma in the NO_PROXY statement variable:

     NO_PROXY="localhost,127.0.0.1,"

Additional Information

libpxbackend-1_0-0.5.3-150600.4.6.2 Released 16th Jan 2025

Change log:

* Tue Jan 14 2025 xiaoguang.wang@suse.com
- Add libproxy-handle-empty-proxy-ignore-entry.patch: Properly
handle empty proxy ignore entry (bsc#1234940).

* Fri Jan 10 2025 alynx.zhou@suse.com
- Add libproxy-ignore-invalid-uri.patch: Ignore invalid proxy URI
to suppress GUri warnings (bsc#1235097).

Note that In earlier versions of SLES 15, a trailing comma in the NO_PROXY statement value, did not cause a segfault issue in zypper.

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.