Pcbnew crashes while attempting 3D view

also, I'm using Ubuntu 64.

Can you please check whether it still happens on Hardy with 2007-11-29a-1 ? I am unable to reproduce at my end. Please confirm.

There is a new version of this package in ubuntu 9.04 Jaunty.
Could you test if this still is an issue there?
Many thanks,

Martin

The bug still exists

Hi, i'm also experiencing the bug in jaunty. I've made a clean install of jaunty a few weeks ago in my ubuntu xps m1330. The segmentation fault happens with and without desktop effects.

$ lspci | grep Graphics
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)
00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)

Thanks,
German.

Hi, it's me again. I just downloaded kicad from its homepage and, as it's recommended there, i installed the files under /usr/kicad. If i run that installation of pcbnew, i can see the 3d render.

Thanks again,
German.

Oh, thank you

same problem as moonkey on exactly the same computer.

problem solved with version from kicad webpage too.
http://kicad.sourceforge.net/wiki/index.php/Main_Page
version 20090216

Kubuntu karmic has 20080825 version, and it crashes when calling 3D View.

Haven't tested with latest version, but don't have time to test in a while.

I'm having the same problem using Karmic.

With kicad-0.0.20080825c-1 pcbnew crashes when opening the 3D View. This happens with and without compiz.

I've tried with the .tar.gz from [1], which is for kicad 20090216 and it works fine, even with Compiz.

This new version of kicad is already Debian testing, as of 10 Oct 2009. I've installed 0.0.20090216-1 0 from the debian repos, and the package seems to work fine, however, it does not fix the problem with the 3D view. It suggests some packaging bug :)

$ lspci
00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 01)

Hope this helps to fix this bug. Thanks,

tulku

[1] http://iut-tice.ujf-grenoble.fr/cao/kicad-2009-02-16-final-UBUNTU_8.10.tgz

I'm using Ubuntu 9.10

I experienced the same as described by tulku on 2009-10-31.

I ended up using the manual installation [1] above.

I hope that this bug is fixed soon, as kicad users need the package to be functioning correctly (and up to date).

ajw@sig3:/usr/local/kicad/bin$ lspci
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 03)

This bug is in Debian (and Fedora) [1], and seems to be isolated to Intel video cards. Please feel free to add to the discussion there and assist the Debian maintainer. Ubuntu syncs kicad from Debian, so it is best to coordinate with them.

[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=477685

I'm still having this problem using Ubuntu 9.10 the Karmic Koala - released in October 2009 and supported until April 2011.

KiCad Version:
Build: (20080825c-final)

Kernel Info:

user@user-desktop:~$ uname -a
Linux user-desktop 2.6.31-20-generic #57-Ubuntu SMP Mon Feb 8 09:05:19 UTC 2010 i686 GNU/Linux

Video Card:

user@user-desktop:~$ sudo lshw -C video
  *-display
       description: VGA compatible controller
       product: 82945G/GZ Integrated Graphics Controller
       vendor: Intel Corporation
       physical id: 2
       bus info: pci@0000:00:02.0
       version: 02
       width: 32 bits
       clock: 33MHz
       capabilities: msi pm bus_master cap_list rom
       configuration: driver=i915 latency=0
       resources: irq:16 memory:e0400000-e047ffff ioport:10c0(size=8) memory:d00

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD of the
development release - Lucid Lynx. It would help us greatly if you
could test with it so we can work on getting it fixed in the next
release of Ubuntu. You can find out more about the development release
at http://www.ubuntu.com/testing/ . Thanks again and we appreciate
your help.

Scott, I've downloaded lucid alpha 2 live cd and tried it in the same machine I've mentioned before (xps m1330, intel video). I still get a segmentation fault whenever I try to see the 3D view (with or without desktop effects).

I don't have much time right now so I didn't upgrade the system. I would like to install lucid instead of running the live cd and then, I could try with the upgraded packages.

Thanks for testing, the live cd should have been enough to see if this
is fixed. According to upstream, the kicad 2009-02-16 should be
working for us (see below
http://<email address hidden>/msg05161.html)

Hi,

I don't know why are you using a 2008 version. Try with
kicad-2009-02-16-final, last stable version.

In a very old version, about 2005, the 3D dislay problem was related with the
color depth stated in the system, 24 or 32 was needed. But now I think it is
not that case.

Pedro.

> Hello Everyone,
>
> I'm using KiCad version Build: (20080825c-final) on Ubuntu Jaunty 9.04. I'm
also using PCBnew Build: (20080825c-final) on the same machines. Out of my 3
machines running the same OS, only 1 runs the 3d Display without crashing.
The other two crash the 3D Display by simply closing PCBnew. Are there any
files that I can look at to get an idea on what is happening?
>
> This also happens when browsing CVpcb, 'view selected footprint', 3D.
>
>
>
>
>
>
>

If anyone has the time, try to install the version from the below ppa:
https://launchpad.net/~showard314/+archive/ppa

The ppa version is the lucid version built against Karmic's libraries

I tried the version posted at https://launchpad.net/~showard314/+archive/ppa
by Scott on a fresh Karmic and 3D worked with no problems.

I have nvidia restricted drivers installed..(just in case it helps to know,

Ch.

Scott, I installed the kicad package in your ppa repository and the result is the same. The segmentation fault is there whenever I switch to 3D view in pcbnew or the component selector (cvpcb). I did this in my xps m1330 (intel video) with and without desktop effects.

For the record, I also downloaded the kicad versions 20080825c [1], 20090216-final [2] and 20100221-rc4 [3] from upstream and they work just fine. 3D view in pcbnew and cvpcb works flawlessly. I installed them under /usr/kicad/.

Could this bug be triggered by some hard coded dependencies or something like that? Because the 3D view gets broken in the packaged version of kicad only.

Regards.

[1] http://iut-tice.ujf-grenoble.fr/cao/old_versions/kicad-full-version-2008-08-25c-final.tgz
[2] http://iut-tice.ujf-grenoble.fr/cao/kicad-2009-02-16-final-UBUNTU_8.10.tgz
[3] http://iut-tice.ujf-grenoble.fr/cao/kicad-2010-02-21-RC4-UBUNTU_9.10.tgz

I forgot to mention that the tests were done under karmic (fully updated).

I've been doing some research with the help of a friend (she's DD!). We compiled the source code from Scott Howard's ppa with DEBUG option and run it within gdb. The backtrace is the following:

Program received signal SIGSEGV, Segmentation fault.
0x00841446 in glMatrixMode () from /usr/lib/libGL.so.1
(gdb) bt
#0 0x00841446 in glMatrixMode () from /usr/lib/libGL.so.1
#1 0x08280315 in Pcb3D_GLCanvas::InitGL() ()
#2 0x0827aa69 in WinEDA3D_DrawFrame::WinEDA3D_DrawFrame(WinEDA_BasePcbFrame*, wxString const&, long) ()
#3 0x08200e3b in WinEDA_PcbFrame::Show3D_Frame(wxCommandEvent&) ()
(...)

The 'glMatrixMode' call is in kicad/3d-viewer/3d_canvas.cpp line 541.

In kicad/COMPILING.txt, there's a comment at the end, that says they are statically compiling with a particular version of mesa. Perhaps that's the reason why the bug doesn't appear when I use the compiled version from upstream.

I'll try to fix this but if there's someone out there who understands mesa, any help will be appreciated.

Thanks for the help. I just packaged Debian's new version, which fixed the bug in Debian. Could you test it with your hardware? Thanks in advance!

https://launchpad.net/~showard314/+archive/ppa

sudo add-apt-repository ppa:showard314/ppa
sudo apt-get update
sudo apt-get install kicad

Hello, i've just tested your package in a live cd of Lucid alpha 2 (the one i have) and it works!!! The 3D render works =)

I hope this could make into Lucid final.

Thanks for all your help.

Release team:
is this even worth trying to get into Lucid (should I apply for an FFe for the sync request)? The upstream changelog change is massive (I can't even find all the changes since there are over a year and a half of commits). Here is a summary of this year alone:

Here are all commits since the last upgrade (all commits since 2/16/2009)
http://kicad.svn.sourceforge.net/viewvc/kicad/trunk/kicad/CHANGELOG.txt?revision=2184
http://kicad.svn.sourceforge.net/viewvc/kicad/tags/kicad-2010-03-14-SVN2456/kicad/CHANGELOG.txt

There are lots of scattered bug fixes and new features.

Debian changelog:
 kicad (0.0.20100314-1) unstable; urgency=low

   * New upstream (Closes: #575018).
   * Update Standards-Version to 3.8.4 (no changes needed).

 -- Richard Antony Burton <email address hidden> Sun, 28 Mar 2010 12:58:23 +0000

Hello to everyone. I'm using Ubuntu 9.10 and I have just the same problem: Pcbnew crashes when I try to open 3D-view. I've thought there's a problem with my video driver (because, I installed KiCad from ppa:showard314/ppa as it was said, and as it works), today I reinstalled and tested it, but the problem remains. Also I tried to install KiCad on Ubuntu 10.04 live, but there it shows unsatisfiable dependencies (apt-get install !!!) libwxbase2.8-0, libwxgtk2.8-0, zlib-bin, extra-xdg-menus. I downloaded them as *.deb from debian repository and after "succsessful" installation I can't start KiCad at all...

Fixed in Maverick.

Hi,

for me, the bug in Maverick still exists.
Build:2010-03-14

$ lspci | grep Graphics
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03)

Bug is back in Maverick on Intel... do we re-open this one, or make a new one?

I think it has to be reopened, because it seems to be the same bug.

terminal output after pcbnew crashes:

The program 'pcbnew' 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 29577 error_code 9 request_code 137 minor_code 8)
  (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.)

/var/log/messages gives: segfault

I also get this message

The program 'pcbnew' 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 29577 error_code 9 request_code 137 minor_code 8)
  (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.)

I am running a Radeon 9600XT with the radeon driver.
It works fine on my Radeon 5770 with the proprietary FGLRX driver from AMD.

Both system are running Maverick 10.10 and Kicad 2010-03-14

Same here:

$ pcbnew
The program 'pcbnew' 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 144802 error_code 9 request_code 137 minor_code 8)
  (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.)

$ lspci | grep Graphics
00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02)

Please reopen. This hasn't been fixed. This looks like an upstream bug as I'm getting it also on my Archlinux system.

I find it quite interesting that for me it:

Crashes on my Radeon 9600XT with the radeon driver,
But works fine on my Radeon 5770 with the proprietary FGLRX driver from AMD.

I don't know what the difference is, why this happens etc.

This bug is still present on Natty. I get the same "BadDrawable" error as described above, using an Intel GMA:

$ lspci|grep VGA
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03)

However, installing the latest nightly build from ppa:paxer fixes the problem, i.e. apparently the bug has been fixed upstream. The build I installed is kicad 2011-07-19-testing.

Thank you!

I've been looking for a KiCAD PPA for a while now, Just installed the new version from 'ppa:paxer' and now 3D is working for me also.

Working for me on: Natty with my Radeon 9600XT, using the radeon\Gallium3D driver.

Works fine in Ubuntu Oneiric.

still might be a problem in lucid

Nov 18 02:07:32 x305 kernel: [174092.780965] pcbnew[3196]: segfault at 0 ip (null) sp bfa3402c error 14 in pcbnew[8048000+6b4000]

video card: GeForce 9700M GTS

I fixed it by using the old 173 driver for the video card.
bzr 3241 btw.