kicad-developers team mailing list archive

[Strontium <strntydog@xxxxxxxxx>]

Extra Information:
The following crash with the X segfault, schematic editor, symbol 
editor, pcb layout editor, footprint editor.  And when they do, they 
kill the project browser.  Gerber viewer also crashes with an X 
segfault, but i doesn't crash the project browser when it does. Bitmap 
to component, PCB calculator and Page layout editor all seem fine.

On 31/10/18 20:42, Strontium wrote:
> I was on the js-reynaud legacy nightly ppa (Ubuntu 18.04), and things 
> were fine a few days ago.  But i just tried to run kicad and it was 
> crashing.
> So, i uninstalled everything from legacy nightly and installed the ppa 
> js-reynaud/kicad-5  but for some reason if i try and open a schematic 
> OR a pcb, it crashes with a segfault also:
>
> Trying to open a schematic:
> > steven@steven-ge40:~$ kicad
> > The program 'kicad' received an X Window System error.
> > This probably reflects a bug in the program.
> > The error was 'BadValue (integer parameter out of range for operation)'.
> >   (Details: serial 8548 error_code 2 request_code 154 minor_code 24)
> >   (Note to programmers: normally, X errors are reported asynchronously;
> >    that is, you will receive the error a while after causing it.
> >    To debug your program, run it with the --sync command line
> >    option to change this behavior. You can then get a meaningful
> >    backtrace from your debugger if you break on the gdk_x_error() 
> > function.)
> > Segmentation fault (core dumped)
>
> Trying to open a PCB:
> > steven@steven-ge40:~$ kicad
> > The program 'kicad' received an X Window System error.
> > This probably reflects a bug in the program.
> > The error was 'BadValue (integer parameter out of range for operation)'.
> >   (Details: serial 4479 error_code 2 request_code 154 minor_code 24)
> >   (Note to programmers: normally, X errors are reported asynchronously;
> >    that is, you will receive the error a while after causing it.
> >    To debug your program, run it with the --sync command line
> >    option to change this behavior. You can then get a meaningful
> >    backtrace from your debugger if you break on the gdk_x_error() 
> > function.)
> > Segmentation fault (core dumped)
>
> Anyone else seen this???  I have no idea what's going on.
>
> Steven