Just gave this a try, but pcbnew also fails immediately.
I'll file a bugreport this evening.
regards,
Mark
Andrew Lutsenko <anlutse...@gmail.com> wrote:
Another good thing to check would be if the issue only happens when
trying
to run pcbnew standalone. If launched from kicad process there should
be no
race since kicad binary doesn't touch any python afaik.
On Thu, May 16, 2019 at 5:53 AM Seth Hillbrand <s...@hillbrand.org>
wrote:
> Am 2019-05-16 06:29, schrieb mdoes...@xs4all.nl:
> > I've seen the following problem for some time when wxpython is
enabled:
> >
> >
>
--------------------------------------------------------------------------------
> > [xcb] Unknown sequence number while processing reply
> > [xcb] Most likely this is a multi-threaded client and XInitThreads
has
> > not been called
> > [xcb] Aborting, sorry about that.
> > kicad: xcb_io.c:643: _XReply: Assertion
> > `!xcb_xlib_threads_sequence_lost' failed.
> > Aborted
> >
>
--------------------------------------------------------------------------------
> >
> > If I disable wxpython everything just works. I suspect it's a
problem
> > with my configuration, since it's almost impossible to start
pcbnew. Is
> > there anyone who has a suggestion where to look?
>
> This looks like a race condition in the wxInit() between python and
> pcbnew. Can you please open a bug report for this?
>
> -Seth
>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help : https://help.launchpad.net/ListHelp
>
_______________________________________________
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help : https://help.launchpad.net/ListHelp
