Moving tracks in PCB 5.99

Hello!
I have a problem when moving tracks.
In fact, I have 2 problems, I just discovered another one.

  1. Moving a via causes the layout editor to crash. I tried to move the one on top right of the first picture below.

  2. I hwanted to use the ‘D’ command. Apparently I have to first select the segment I want to move. Then pressing D works, but as soon as I click to lay the track, both ends are erased. A few pictures to illustrate this. I would like to move the 45 degree track on top left.

Screenshot from 2021-06-04 18-18-31

After moving the 45 degree track, as soon as I release the mouse button, only the 45 degree track remains, the tracks at the 2 ends disappear and are replaced with the correspondng ratsnet lines.

Screenshot from 2021-06-04 18-17-24

Is this a new bug? I used 5.99 a few times, and I don’t remember that kind of problem. I use the D command quite a lot, so I guess it’s not possible that I didn’t notice earlier. I’m using Ubuntu 21.04, and the Kicad version is the one automatically updated with Ubuntu, this morning.

Thanks,

It’s possible. @twl recently committed changes to the PNS router. That’s not the simplest part of KiCad code and bugs are almost inevitable. Please create bug reports, preferably with the project with which the problems can be repeated.

Hello!

Unfortunately, I cannot publish the file. For the time being, I’m playing with the same file in 5.1.9 and 5.99 in parallel. 5.1.9 is for work, 5.99 is for experiment. As for bug reports, I’m not sure of what you want me to do. If this is not a bug report, what is it?

Issues aren’t tracked here, they are in the gitlab issue tracker. https://gitlab.com/kicad/code/kicad/-/issues

If possible, create a smallest possible design which shows the problem. It doesn’t have to be the original, you can create one from scratch or reduce a copy of the original to a minimum by deleting as much as possible, still leaving the problem visible.

You can create a bug report on Gitlab, as @eelik said, attach the layout and mark it as confidential. You don’t have to publish the PCB, it will be only accessible to the lead developers. I’m afraid I won’t be able to help you otherwise.

Tom

@roboya how do you perform via move? What hotkey/mouse operation are you doing?
What are your interactive router settings?
Maybe the bug is easily reproducible on standard designs.

This is probably a duplicate of bug:


It was solved yesterday I think.

Hello!
Thanks for your replies. I would like to update and check if it works, but I’m stuck with Jun 1 version. Maybe because I have upgraded Ubuntu to v. 21.04. Are there packages to download instead of using the software updater? When looking at the download page, the only solution is the apt-get intall terminal. Or is there any way to force a newer version?
Thanks,

Are your KiCad PPA sources.list entries up to date, i.e.

deb http://ppa.launchpad.net/kicad/kicad-dev-nightly/ubuntu hirsute main 
deb-src http://ppa.launchpad.net/kicad/kicad-dev-nightly/ubuntu hirsute main

Hello!
Thanks for you reply . Apparently not.
cat /etc/apt/sources.list | grep -v ‘#’
gives me the output hereafter.
What should I do? Add the above 2 lines manually?
By the way, I will not compile kicad. Do I need the deb-src line?

Thanks,

deb http://jp.archive.ubuntu.com/ubuntu/ hirsute main restricted
deb http://jp.archive.ubuntu.com/ubuntu/ hirsute-updates main restricted
deb http://jp.archive.ubuntu.com/ubuntu/ hirsute universe
deb http://jp.archive.ubuntu.com/ubuntu/ hirsute-updates universe
deb http://jp.archive.ubuntu.com/ubuntu/ hirsute multiverse
deb http://jp.archive.ubuntu.com/ubuntu/ hirsute-updates multiverse
deb http://jp.archive.ubuntu.com/ubuntu/ hirsute-backports main restricted universe multiverse
deb http://security.ubuntu.com/ubuntu hirsute-security main restricted
deb http://security.ubuntu.com/ubuntu hirsute-security universe
deb http://security.ubuntu.com/ubuntu hirsute-security multiverse

What I would do:

  1. Uninstall the version you have now.
  2. edit your sources.list and comment out the lines related to KiCad (or remove them completely after you backed up that file.
  3. Follow the instructions on the KiCad website to install from the js-reynaud repositories.

Hello!

Thanks for your reply.
For 1: I did sudo apt-get --purge remove kicad-nightly
For 2: As there are no “kicad” in the whole file, I left everything as is.

Whatever I do, when I restart kicad, then get info, I get this:
Build Info:
Date: Jun 1 2021 08:39:02
wxWidgets: 3.0.5 (wchar_t,wx containers,compatible with 2.8) GTK+ 3.24
Boost: 1.74.0
OCC: 7.5.1
Curl: 7.74.0
ngspice: 34
Compiler: GCC 10.3.0 with C++ ABI 1014

Is there a way to have yesterday’s build with Ubuntu 21.04. Just curious: is anybody out there using it?

Thanks,

Hi, I see the same problem. Suddenly the Ubuntu (18) PPA stopped working, it got stuck on June 1st.

So I had to compile KiCad from source xD to solve this bug.

Oops.
For me they ended up in:

paul@medion:/etc/apt/sources.list.d$ ls
freecad-maintainers-freecad-stable-focal.list
kicad-kicad-5_1-releases-focal.list
kicad-kicad-dev-nightly-focal.list
official-package-repositories.list
paul@medion:/etc/apt/sources.list.d$ cat *kic*
deb http://ppa.launchpad.net/kicad/kicad-5.1-releases/ubuntu focal main
# deb-src http://ppa.launchpad.net/kicad/kicad-5.1-releases/ubuntu focal main
deb http://ppa.launchpad.net/kicad/kicad-dev-nightly/ubuntu focal main
# deb-src http://ppa.launchpad.net/kicad/kicad-dev-nightly/ubuntu focal main

dpkg is a low level interface to package management, and I think you can download packages with it without installing and install them later at will, but I have not really used it. Just as commands like apt-cache.

I also think that during the normal install process the uninstalled packages are kept in a cache somewhere.

In linux you can do all kinds of fancy tricks with package management, and if you want to know more, then start with some kind of tutorial.

Ubuntu has /etc/apt/sources.list.d/ and there files for PPA sources.list lines. Check out the one for kicad.

It’s of course possible that there’s some problem in the PPA repo itself, but there seem to be newer files there.

Hello!
Thanks for your reply. The problem is that I don’t know what is normal and what is not.

Screenshot from 2021-06-05 18-50-04
image

The lines in these files look like one file has been generated per valid line of /etc/apt/sources.list,
but I don’t know why, so I don’t feel like messing with it.

You have js-reynaud ppas there, do you really need them? The rest seem to be for groovy (20.10). Are these in /etc/apt/sources.list.d/ ? If yes, just delete them all and add again only those you need, following the instructions so that they will be for hirsute.

Hello!

Thanks for your reply!

Short reply: I don’t know! As said above, I don’t know what is normal or not. Usually, when I write software I do it so that the dumbest among the dumbest can use it, that you don’t even have to install it. You put it wherever you want and it just works. That said, I happend to find exceptions a few times, especially a guy whom I told to create a <user_name>/Data folder and he did actually create C:\users\<username>\Data (I mean he created a folder called “<username>”. As for Kicad, there is a page explaining how to install, and I could do it by copy - paste of the instructions in the terminal. When using Linux, I feel like the above average <username>.

Yes!

How do I know “those I need”? Why should I add again those I need and not directly delete only those I don’t need? Well, in this case also I have to know those I don’t need. Looks like a circular nightmare.

Where do I find these instructions? There are very few hirsutes around me.

Thanks,

This is likely not your issue but…

I’m using Windows 10/64 with nightly’s. I had a similar issue and found there was a layout error where the trace was too close to something else (having trouble recalling the details). My trace would disappear when I attempted to move it.

My solution was to delete the trace and some connecting traces then re-adding them. Cleared everything up.
Likely not your issue but should be easy to try.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.