X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
Message-ID:	<5044610B.5030305@estechnical.co.uk>
Date:	Mon, 03 Sep 2012 08:49:31 +0100
From:	Ed Simmons <ed AT estechnical DOT co DOT uk>
User-Agent:	Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20120714 Thunderbird/14.0
MIME-Version:	1.0
To:	geda-user AT delorie DOT com
Subject:	Re: [geda-user] PCB exits when doing DRC
References:	<20120809091636 DOT 493cd1d0 AT wind DOT levalinux DOT org> <CAHBVutB4dxHire=qatW=KRs4dSUEL5HcZ-_aaVg8DTznJ+_71w AT mail DOT gmail DOT com> <1344544333 DOT 81713 DOT YahooMailNeo AT web120702 DOT mail DOT ne1 DOT yahoo DOT com> <50441823 DOT 1050601 AT cox DOT net>
In-Reply-To:	<50441823.1050601@cox.net>
X-Authenticated-As:	ed AT estechnical DOT co DOT uk
Reply-To:	geda-user AT delorie DOT com

On 03/09/12 03:38, Lloyd Strickler wrote:
> I've started on a new pcb layout and found that the application exits 
> without warning when doing a DRC check. I went back to a previously 
> checked board and it does the same thing now. I just updated the 
> application from git today and it didn't change it's response.
>
> I've attached the smaller file that is causing this.
This happens here too... I'm using an nVidia graphics card with mesa 
driver under ubuntu 11.04. I have the geda project in my own SVN server 
and regularly git pull the changes.failed to create pixmap
I've just git pulled the latest changes and tried the DRC checker out 
again. The problem first arose for me when I had to switch from the 
'proper' nvidia drivers to the mesa drivers/

Run from a shell here's the error I get.

The program 'pcb' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadDrawable (invalid Pixmap or Window parameter)'.
   (Details: serial 24661 error_code 9 request_code 55 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.)


Ed

- Raw text -