pcbnew crash in lucid

Bug #557918 reported by alsercol on 2010-04-08
This bug affects 4 people
Affects Status Importance Assigned to Milestone
kicad (Ubuntu)

Bug Description

Binary package hint: kicad

pcbnew kills x-server in lucid when I open a pcb file

Scott Howard (showard314) wrote :

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!


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

Changed in kicad (Ubuntu):
status: New → Incomplete
alsercol (alsercol) wrote :

Thanks for your package, Scott.

I have been checking your new version in the ppa but I have the same bug: when I open a file with pcbnew x-server kills and I have to re-login.

I think it's a display driver bug, because with the nvidia-173 driver pcbnew works OK.

I'm using Lucid, 64bit version and nvidia GeForce 8600GS.

peter eiso (petereiso) wrote :

g'day chaps 'n chapesses

I too have run into this problem. When I try to open an existing design in pcbnew, it throws me back to the login screen. This only happens on some designs but not on all.

I installed kicad on another lucid gnome machine and that opens them fine. A different video adapter, so the driver bug theory may be right.



brawd (bengy103) wrote :

As a variation of event what happens is I get booted out when I try to zoom in at the pcbnew screen.

Nvidia drivers (of course) seems to be involved (again).



Kicad Is one of my favorites.
I too have that problem.
the circumstances are :
1.Ubuntu 10(i386 and amd64 both).
2.kicad(2009 version and 2010 version at least.I don't know about other versions.)
4.when PCB contains any **(ARC)** type line(for example a module wich have an arc border(blue) line in it).
5.when you try too change the viewpoint on that segment(forexample zoom in or out).

as far as I examined the situation ,these were what caused the problem,and that bug wont happen on any other circumstances.
so you may see that problem with some pcb file and not with all pcb files.
and I don't think that bug has any thing to do with Graphic card(my graphic cart is ATI EAX1950 pro).

since Kicad Is one of my favorite programs I hope that bug will be fixed soon.

It's happening to me, too. I've used three versions; one from 2008, 2009 (in the repos), and the most recent 2010. I've also compiled 2010, and the ppa listed above, with the same results.

I also have an oooold ATI card in my laptop (radeon mobility 9600...and it doesn't have any true drivers for it anymore), so I don't think it's the video drivers. (though I'm going to see if there's something else available for this old card...)

These are the errors I've been able to collect:
~$ pcbnew > output.txt 2>&1 &
pcbnew: Fatal IO error 104 (Connection reset by peer) on X server :0.0.

and from /var/log/syslog
kdm[777]: X server for display :0 terminated unexpectedly

hi every body.
have any one of you tested that if whether that bug will happen on a pcb which doesn't have any arc type line(not circle line)
in it?
I seriously think that the bug have something to do with arc lines.
Best wishes.


I initially dismissed the idea b/c I thought I *didn't* have arcs in the designs I was testing, but all of them did (silly LEDs!).

I'll have to try it tonight, when I get home. Just a simple schematic with a few resistors should do it :)

I tried it out, notreallyimportant.

I didn't play with it for a great while, but a schematic comprised of a single resistor and TO220 never crashed. For kicks and giggles, I opened the module editor, and loaded a DIL-40-ZIF-Socket from the Sparkfun library (converted from Eagle; what I'm using in my current project). It opened, but as soon as I zoomed in, everything crashed -- there's an arc at the "top", just like a DIP IC.

This also goes in line with the few times it took a while to crash -- I was zoomed in on other components w/o arcs, but as soon as I moved to look at the ZIF socket, it crashed.

What could be causing it to crash for some people in Lucid, but not others?

(I'm also downloading the windows version to see if it runs in WINE, and if so, whether or not pcbnew crashes the system from there, too)

Confirmed crashing while running the windows version via WINE.

How's the rendering done in pcbNew? What's so "special" about arcs?

Changed video driver to "vesa", and despite the horrible display, pcbnew doesn't crash.

Something in the DRI drivers, perhaps? (but our friends above mention nvidia, too)

yes,it is too strange.
so are you sure that the bug wouldn't happen on anything else than arcs?
maybe it is because of the way that pcbnew sends arcs data to graphic driver and the way that the driver deals with the data(since that bug won't happen on circles)maybe they don't match!
I don't think this is kicad's fault.and I don't think this is the graphic driver's fault also, since I think Ubuntu 10 and 9 have the same graphic driver(I am not certain about it).I may not have enough programming knowledge but I think there is some thing between pcbnew and the graphic driver and that thing doesn't work properly in lucid,and if I am right about it then we may see another erors and crashings in other graphical programs which using arcs! although it depends on the way that they use to send arcs data.
best wishes.

Stefan Carslöv (odur) wrote :

I get the same type of crash in eeschema every time I try to add a component with an arc in it (e.g CP1)
Screen goes black and then I'm back to KDM.

Kubuntu Lucid with KDE 4.4.4

Launchpad Janitor (janitor) wrote :

[Expired for kicad (Ubuntu) because there has been no activity for 60 days.]

Changed in kicad (Ubuntu):
status: Incomplete → Expired
Peter Clifton (pcjc2) on 2010-12-07
Changed in kicad (Ubuntu):
status: Expired → Confirmed
Nick Østergaard (nickoe) wrote :

Lucid is not supported on the desktop anymore.

Changed in kicad (Ubuntu):
status: Confirmed → Incomplete
Launchpad Janitor (janitor) wrote :

[Expired for kicad (Ubuntu) because there has been no activity for 60 days.]

Changed in kicad (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers