Bug#913864: KiCad is not usable, because cvpcb is not working
Hello Carsten, Am 29.11.20 um 07:17 schrieb Carsten Schoenert: > Hello Karsten, > > next time please start a new bug report. Now there is a cloned old > report there the old history is completely indpendent from your issue. > This makes it not easier to follow the red line. O.K. >> i am talking about the features behind the button "Assign PCB >> footprints to schematic symbols" (see screenshot). > It's obvious to me what you are talking about. I know what CvPcb is > doing. Not for all of us under every circumstances. >> Fact is that this part of KiCad seems to be very buggy. > I disagree. I don't know any upstream bug report about CvPcb or from the > KiCad forum from about the last two years. But you can see the reported bugs. You can define them as nonsense, but that will not fix the problem. > If you think your issue is related to the original report why don't you > have written about this in first place? The other report has a lot of > information how the library symbol clashing can be found and which > library/symbol is the right combination. Have you really tried out these > steps at your own? This all makes no difference when you say it is running for you and there is no bug. >> It's fine that it is running stable on your system. >> But this is no explanation that it must be stable everywhere. >> On the other hand i think that you can't do anything to solve this bugs. > If your issue is really a upstream issue than it needs to be reported > to the upstream developers. The KiCad team is really responsive and quick > to fix such things once they have understand what problem is responsible > for the visible behavior. The standard answer from developers is: "Have you tried the actual version". There is no support of bugs in older versions as used in an stable distribution. This point of view is understandable, but does not help the user. > >> We must wait until this bugs are solved in newer versions of Kicad. >> Version 5.1.8 seems to be on the way ... > You mean 5.1.9 for sure. I mean 5.1.8+dfsg1-1~bpo10+1 from the backports. We will see what will happen in later releases. > > I believe this report will start bit rotting, searching a possible issue > in this rather old version is exhausting and mostly useless in my eyes > as the current supported version is 5.1.8. Yes - thank you for your support so far! > Te current rules of the > release team makes it hard to update the version of kicad in stable due > rather big source code changes that are not related to the baisc rules > for updates of packages in stable. > I don't have really time to jump into work which nobody will use and > honor somehow in the end. That's understandable. Besides Debian 10 is running less stable than Debian 8. There are many detail issues, but Debian 8 is not supported any more ... An upgrade to testing did fail too - maybe it is possible now. > You have found a newer version in backport where you don't have problems > with. And the backports archive is exactly the use case for newer > versions with newer and improved features like KiCad upstream does within > their release for the stable cycle. Yes - but first i didn't remember to look at the backports. It seems new that the pinning does not automatically update to a newer version when it exists. So it must be done manual for every main package. Best regards karsten
Bug#913864: KiCad is not usable, because cvpcb is not working
Control: notfound -1 5.0.1+dfsg1-3 Control: tags -1 - wontfix Control: notfound 913864 5.0.2+dfsg1-1 Hello Karsten, next time please start a new bug report. Now there is a cloned old report there the old history is completely indpendent from your issue. This makes it not easier to follow the red line. Am Sun, Nov 29, 2020 at 02:49:38AM +0100 schrieb Karsten: > i am talking about the features behind the button "Assign PCB > footprints to schematic symbols" (see screenshot). It's obvious to me what you are talking about. I know what CvPcb is doing. > How this simple part of KiCad cannot be used as intended? > Using the wrong hand for the mouse? :-) Simple things can be difficult if you don't know what the right is thing to do is clear to you. You say "It doesn't work", I've tested CvPcb from 5.0.2 with some of my projects and I don't see a problem, I can assign footprints what ever I like to assign. I can set the filtering from no filtering to the most strict filterung which is the only thing that has impact to the visible list with the footprints on the right. I have no idea what the point is where you assume CvPcb is broken. How can I readjust your situation? What your are doing (and what not). What other package you might have installed from backports or third party repositories which might have a bad interact with kicad from stable? But I don't think this is happen in any way. Any third party plugin installed which might have impact on your side? > Fact is that this part of KiCad seems to be very buggy. I disagree. I don't know any upstream bug report about CvPcb or from the KiCad forum from about the last two years. And I don't know some Git related history about bug fixing in this area within the 5.1 cycle. > I did not open a new bug report for it, because i thought the problems > of the described problem are to similar. > One time this part crashed, but this was really not reproducible. If you think your issue is related to the original report why don't you have written about this in first place? The other report has a lot of information how the library symbol clashing can be found and which library/symbol is the right combination. Have you really tried out these steps at your own? > It's fine that it is running stable on your system. > But this is no explanation that it must be stable everywhere. > On the other hand i think that you can't do anything to solve this bugs. If your issue is really a upstream issue than it needs to be reported to the upstream developers. The KiCad team is really responsive and quick to fix such things once they have understand what problem is responsible for the visible behavior. > We must wait until this bugs are solved in newer versions of Kicad. > Version 5.1.8 seems to be on the way ... You mean 5.1.9 for sure. I believe this report will start bit rotting, searching a possible issue in this rather old version is exhausting and mostly useless in my eyes as the current supported version is 5.1.8. Te current rules of the release team makes it hard to update the version of kicad in stable due rather big source code changes that are not related to the baisc rules for updates of packages in stable. I don't have really time to jump into work which nobody will use and honor somehow in the end. You have found a newer version in backport where you don't have problems with. And the backports archive is exactly the use case for newer versions with newer and improved features like KiCad upstream does within their release for the stable cycle. Regards Carsten
Bug#913864: KiCad is not usable, because cvpcb is not working
Hi, Am 28.11.20 um 11:17 schrieb Karsten: i have made my circuit diagram, but cvpcb is not working. The window opens, but when you click on a library, the component list is not actualized in the window right. So you can't assign the footprints to the components. KiCad is unusable, because at this point you can't proceed to layout. I can't reproduce this behavior. Seems to me you didn't use CvPcb the way it is intended. And btw., your message about your potential problem is completely wrong in this report. -- Regards Carsten
Bug#913864: KiCad is not usable, because cvpcb is not working
Package: kicad Version: 5.0.2+dfsg1-1 Severity: important Hello Carsten, i have made my circuit diagram, but cvpcb is not working. The window opens, but when you click on a library, the component list is not actualized in the window right. So you can't assign the footprints to the components. KiCad is unusable, because at this point you can't proceed to layout. Best regards karsten -- System Information: Debian Release: 10.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-11-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
