X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Date: Sun, 13 Jun 2021 13:25:52 +0200 (CEST)
From: Roland Lutz <rlutz AT hedmen DOT org>
To: "Claudio Fabri (clafi AT gmx DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Subject: Re: [geda-user] PCB can no longer imports schematic
In-Reply-To: <trinity-173a0efa-ea79-4f07-b77a-b9c93a0d3d83-1623444822237@3c-app-mailcom-bs16>
Message-ID: <alpine.DEB.2.21.2106131312150.18206@nimbus>
References: <trinity-f4e69ccb-b2bb-4ee0-85c3-f30957761225-1623237572882 AT 3c-app-mailcom-bs08> <alpine DOT DEB DOT 2 DOT 21 DOT 2106091750380 DOT 8283 AT nimbus> <trinity-173a0efa-ea79-4f07-b77a-b9c93a0d3d83-1623444822237 AT 3c-app-mailcom-bs16>
User-Agent: Alpine 2.21 (DEB 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Reply-To: geda-user AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: geda-user AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

On Fri, 11 Jun 2021, Claudio Fabri (clafi AT gmx DOT com) [via 
geda-user AT delorie DOT com] wrote:
> I cleaned the cache and restarted gnetlist --list-backends, same (kind 
> of) error.

That's actually a quite different error.

Running gnetlist on a fresh install (or after removing the Guile cache) 
has sometimes led to problems; Guile appears to compile files differently 
depending on the execution environment.  (*sigh*)  I tend to run gschem 
first so Guile compilation happens correctly.  That said, this doesn't 
appear to be the problem here.

> ERROR: Throw to key `python-exception' with args 
> `("exceptions.UnicodeDecodeError" "'ascii' codec can't decode byte 0xc3 
> in position 59: ordinal not in range(128)")'.

> Failed to load RC file [gafrc]

I have tried different things to reproduce this error, and while I did 
find several different bugs (I really should do mean things to gEDA/gaf 
more often), I couldn't reproduce your problem.

The most probable cause is a non-ASCII character in a place where gEDA/gaf 
doesn't expect it.  If you have any special characters in your pathname, 
"gafrc" file, or similar, maybe you could test if the problem goes away 
(or the error message changes) if you remove this character?  Knowing 
where the error comes from would be very helpful in solving the issue.

Roland