Problem with psconvert on pyGMT

I don’t, although this all started before conda so I think the problem isn’t conda in particular. I do have it working on my Linux machine though, doesn’t give us much about where the problem is but just in case.

This seems to indicate that first error is before first call to ghost (the Find HiResBoundingBox)

… and a new ghost

System call [@"C:\Program Files\gs\gs9.54.0\bin\gswin64c.exe" ...

It does seem weird the place where the first error appears, but I don’t know what it means. The new ghost is because I wanted to test if it was a problem with the conda provided one, but hiding it and using an official install gives the exact same error

So, in summary, this does not seem to be a ghost issue since it occurs with different installs and happens before ghost system call but stil points to psconvert because you also get the error when running a plain psconvert command on a PS file, right?

Correct, both gmt and ghost are running alright (as far as I can tell), but when the former tries to call the latter, chaos ensues. Or maybe it’s specifically psconvert, but I don’t know if there’s other commands that call ghost through gmt just to try that.

Thanks for helping debug this but further help at this time only if I could reproduce the problem and catch it in the debugger.

Thank you for your time! I really have no idea how to reproduce it. I’m beginning to think it’s something to do with the sessions dir, maybe some sort of protection that it has, as trying to clear the sessions keeps giving me an error

(pygmt) C:\Users\fedes>gmt clear sessions
El sistema no puede encontrar la ruta especificada.
clear [ERROR]: Failed to remove session directory C:/Users/fedes/.gmt/sessions [error = 1]

Although the command does clear the session, I don’t know why that error is popping up.

It’s not unlikely that it may come from trying to remove some tmp file that no longer exists, but this opens a new question. If that error message is not fatal then why the gswin64c system call fails? Same thing, no luck without debugging.

I had the same problem with pure gmt6 on my Ubuntu 25.10 system. Here, AppArmor disallows gs to read files from ~/.gmt/sessions/*.

I fixed that with

sudo aa-disable /usr/bin/gs