On 11/26/18 4:57 PM, Steven A. Falco wrote:
> On 11/26/18 3:30 PM, Simon Richter wrote:
>> Hi,
>>
>> On 26.11.18 17:52, Steven A. Falco wrote:
>>
>>> Since I am one of the packagers for KiCad for Fedora, I get "abort" reports 
>>> that Fedora has collected from users.
>>
>>> I'm forwarding one of the reports to see if there is any interest in this 
>>> data by any KiCad developers.  Please let me know if it is helpful, or if I 
>>> should just disregard these abort reports.
>>
>> We've had a similar report on IRC a week ago.
>>
>> - Is that KiCad 4.0.7, or the 5.0 series?
>> - Did the kicad package or one of its dependencies change in the last
>> days (because it looks like we have >10 reports in just two days).
>>
>>    Simon
>>
> 
> I'd guess that this is the 5.0 series, because the bug was reported in Fedora 
> 29, and 4.0.7 is not available for Fedora 29.  But someone might have 
> installed an older kicad manually, though.  I'll try to get more information. 
>  What the web page shows is very sketchy.
> 
> As to what else might have changed, these are the dependencies shown in the 
> back-trace:
> 
> Nov 19th      lib64/libc.so.6
> No change     lib64/libgdk-x11-2.0.so.0
> No change     lib64/libglib-2.0.so.0
> No change     lib64/libgobject-2.0.so.0
> No change     lib64/libgtk-x11-2.0.so.0
> No change     lib64/libwx_baseu-3.0.so.0
> No change     lib64/libwx_gtk2u_core-3.0.so.0
> 
> So only libc changed - on November 19th.
> 
> If I get more info I'll let you know.

I haven't found a way yet to get detailed data from the high-level "Fedora bug 
reporter" web site, but I did find a number of KiCad bugs logged in Fedora's 
Bugzilla.  Some of them were created by the ABRT tool, but none are from KiCad 
5.  In general, it looks like most of the reported bugs are related to DRC 
crashes in KiCad 4.0.7.  There is a lot more detail in the individual bugs if 
anyone cares to look:

bug 1507256     kicad-4.0.7-2.fc27      2017-10-28      Claimed that modules 
like "through hole resistors" are missing

bug 1571856     kicad-4.0.7-1.fc27      2018-04-25      Moving components in 
eschema or pcbnew (using the default canvas) causes a complete application crash

bug 1577065     kicad-4.0.7-3.fc28      Sun 09:30       When running design 
rules check (DRC) in KiCAD's pcbnew tool, the application crashes completely.

bug 1577671     kicad-4.0.7-3.fc28      2018-05-13      after finishing routing 
my pcb layout i run the DRC and it sudnely freezes kicad and kicad exits

bug 1586192     kicad-4.0.7-3.fc28      2018-06-05      Whe i've tried "Start 
DRC"

bug 1596959     kicad-4.0.7-3.fc28      2018-06-30      Pcbnew -> Perform 
design rules check -> Start DRC. The program crashes

Is it the team's policy that no remaining 4.x bugs will be fixed?  If so, it 
might make sense to annotate the bugs, indicating that users should upgrade to 
5.x.  Please let me know.

        Steve

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Mailing list: https://launchpad.net/~kicad-developers
Post to     : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Reply via email to