[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
gEDA-user: GTK PCB crashes with losing the data
- To: geda-user@xxxxxxxx
- Subject: gEDA-user: GTK PCB crashes with losing the data
- From: Karel Kulhavy <clock@xxxxxxxxxxxxx>
- Date: Sun, 26 Mar 2006 10:21:10 +0200
- Delivered-to: archiver@seul.org
- Delivered-to: geda-user-outgoing@seul.org
- Delivered-to: geda-user@seul.org
- Delivery-date: Sun, 26 Mar 2006 03:53:57 -0500
- Reply-to: geda-user@xxxxxxxx
- Sender: owner-geda-user@xxxxxxxx
- User-agent: Mutt/1.5.11
I was drawing a schematic. Suddely PCB crashed with the following errors
and destroyed my unsaved work. The windowmanager is fvwm. pcb-bin:
20050609
I don't know whether the "** Message: GotoError: ChangeGroupVisibility
(GetLayerNumber" errors were produced during the crash or during
previous work.
clock@kestrel:~/creat/ronja/trunk/schematics$ pcb twister2.pcb
** Message: GotoError: ChangeGroupVisibility (GetLayerNumber
** Message: GotoError: ChangeGroupVisibility (GetLayerNumber
** Message: GotoError: ChangeGroupVisibility (GetLayerNumber
** Message: GotoError: ChangeGroupVisibility (GetLayerNumber
The program 'pcb-bin' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
(Details: serial 25054107 error_code 1 request_code 0 minor_code 0)
(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.)
The program 'pcb-bin' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
(Details: serial 25054110 error_code 1 request_code 0 minor_code 0)
(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.)
CL<