Mailinglist Archive: opensuse-factory (1578 mails)
| < Previous | Next > |
Re: [opensuse-factory] How to segfault zypper
- From: Dimstar / Dominique Leuenberger <dimstar@xxxxxxxxxxxx>
- Date: Fri, 25 Nov 2011 09:11:40 +0100
- Message-id: <1322208700.2770.1.camel@3120-3560.ams.tmf-group.com>
On Fri, 2011-11-25 at 08:25 +0100, Bruno Friedmann wrote:
Hi,
the first thing I (as libproxy maintainer) would want to verify / circle
in would be if libproxy is the 'cause' or zypp.
Can you, as root, simply try to issue
proxy http://www.google.com
(proxy is the libproxy ref implementation, coming from the package
libproxy-tools).
if this crashes as well, make sure to create a bnc entry, add a
backtrace, a copy of your sysconfig/proxy file and some cheese (Want to
make a fondue).
Thanks a lot,
Dominique
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-factory+owner@xxxxxxxxxxxx
I just discover (after looking around) to find the culprit of using my
internal proxy for browsing internal data.
Zypper use libproxy, and this one is affected by the content of
/etc/sysconfig/proxy.
if you place a CIDR address
zypper segfault badly (with zypper ref -f for example
Hi,
the first thing I (as libproxy maintainer) would want to verify / circle
in would be if libproxy is the 'cause' or zypp.
Can you, as root, simply try to issue
proxy http://www.google.com
(proxy is the libproxy ref implementation, coming from the package
libproxy-tools).
if this crashes as well, make sure to create a bnc entry, add a
backtrace, a copy of your sysconfig/proxy file and some cheese (Want to
make a fondue).
Thanks a lot,
Dominique
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-factory+owner@xxxxxxxxxxxx
| < Previous | Next > |