There is not any not-polite phrase to tell “this issue is not addressed”. Where do you see the “unpolite”?
this issue is very known and it’s not impolite to tell that the final result is awful . This was already debated on other topics in this forum and all they used the same terms. All of them are “impolite”?
For what it’s worth I colored your SVG using InkScape and imported it. The hole is still filled but I wasn’t able to reproduce the crash you got. If you have an SVG which crashes Pcbnew it’s probably a good idea to report that and upload the SVG.
Ok I notice they didn’t addressed the issue with the SVG at all. It still there since one year and more.
Here, you are complaining about the length of time an issue has existed, implying you think it is not reasonable that we didn’t prioritize SVG importing more. The team has many priorities, and improving the importing of logos is lower down the list than some other things, especially since for most people, the bitmap converter works just fine.
No, the issue isn’t known to the developers. There is no open issue that I can find describing problems with the bitmap converter. I’m talking to you, about this forum thread. If other threads were also using that language, yes they would be impolite.
Hi Albin can you try with the one here in attachment please?
It’s not colored but it makes PCBNew crash
Sure, but I’m not finding the attachment you’re referring to. Did you miss attaching it?
Strange because here it’s very known that the Bitmap converter doesn’t get great result and therea re several imprecisions into the conversion, making the final result awful.
So from what you say, I understand many ones got this issue but no one yet informed the developers?
On the other hand, many people use the bitmap converter successfully and have no complaints.
As I said before: if you have a problem with the bitmap converter, you need to file an issue on GitLab showing the input, the output, and describing the problem you have. I cannot find any existing reports about this.
For issues to be fixed, they generally need specific reports that describe the problem and the expected behavior, ideally with test cases that show the problem. At the very least that makes them easier to diagnose and fix, which translates into them being fixed faster and more completely.
(I’m speaking generally as an engineer here; this is not KiCad-specific)
1 Like
OMG I did upload I see (editing the message) there is the line pointing to the file, but I don’t see it when I read the published message. I retry here as ZIP instead
ELETTRONICI-ENTUSIASTI.zip (3.1 KB)
Because it is a white square 
I can confirm that importing this SVG in 6.0.2-98 in Windows 10 makes Pcbnew crash.
The SVG seems to contain only a bitmap? I’m no expert in vector graphics but the resolution seems very low and I’m not able to ungroup the text in Inkscape.
I’m guessing that bitmaps in SVGs isn’t supported, but it shouldn’t make Pcbnew crash. Please report the issue if it’s not already reported.
Edit: It also opens fine in Chrome, Edge, LibreOffice Drawn and Inkscape.
1 Like
I installed 6.99 and got the same result as in 6.0.2-98-g5cc2bef954.
Your first SVG imports but there’s no hole in the P. Your second SVG causes Pcbnew to crash.
Application: KiCad PCB Editor (64-bit)
Version: (6.99.0-1051-gcb16ad7557), release build
Libraries:
wxWidgets 3.1.5
FreeType 2.11.1
libcurl/7.78.0-DEV Schannel zlib/1.2.11
Platform: Windows 10 (build 19042), 64-bit edition, 64 bit, Little endian, wxMSW
Build Info:
Date: Feb 23 2022 19:16:57
wxWidgets: 3.1.5 (wchar_t,wx containers)
Boost: 1.76.0
OCC: 7.6.0
Curl: 7.78.0-DEV
ngspice: 36
Compiler: Visual C++ 1928 without C++ ABI
Build settings:
KICAD_USE_OCC=ON
KICAD_SPICE=ON
1 Like
yes I think this was a kind of wrong export I have made. SVG with merged elements, and KiCAD doesn’t recognize them. It’s fine but it shouldn’t crash.
Thank you for the double check 
No problem.
Please note that I haven’t reported either of these issues. The crash needs a new issue report, the missing hole can possibly be reported on the already closed issue (I’m not sure what’s preferred). I saw that you commented on the commit, but you should probably comment on the issue as well.
They blocked the commenting I can’t add details … ah … about “politeness”? …
Just the attitude “”“to me doesn’t happen so it’s your fault, go away”""
Then it’s probably preferred that a new issue is created. I wasn’t sure.
I’ve never experienced that attitude. But there’s over a thousand issues reported and others may not have the same priorities as you. Just be patient and find a workaround in the meantime.
I am patient. but asking for a file, wanted to comment adding it, closing the commenting and the issue, it’s way more impolite han telling what it is: this issue was not addressed.
yes perhaps similar ones, but not this in particular. Not only that: the crashing of the system is also a fact. It occurs. So, what’s the problem to investigate to try to understand the reasons, rather than to close the issue? bah …
We have enough information to fix the issue and it will be fixed in due time. You are not the KiCad project manager and the timeline of fixing issues is not up to you. I blocked you on the bug tracker because I doubt there’s anything your remarks would further contribute to the discussion. And, yes, it’s about politeness.
Tom
1 Like
yes I see it is about politeness. Who wants to teach it, seems it’s fully missing the track.
I didn’t tell: I’m the PM of the project nor the time-line about. Those are your words. Not mine!
I’m a client and, as customer, I just notice this issue is not yet solved. And yes: I do notice that it’s opened since a long while.
It has nothing really nothing to do with politeness or not. Just as client/user, it seems it’s not yet tackled. Like it or not. This is what’s is perceived. It’s up to you to tell us the reality and to explain us the details. Not up to us to have the crystal sphere.
Yes: you closed the topic. But up there somebody else asked to upload the file that created the crash.
Fortunately I could at least edit the topic adding it. I didn’t know I could. Just i tried and it worked.
In the first instance, I was trying responding to the person, uploading the requested file.
As you want/claim we, customers, should imagine what there is “behind the scenes” upfront we express ourselves, I think you need also to understand us, as users. When we highlight something that for us is important. For you not. But for us: yes. Not for this, “we are impolite”. Enjoy your day, sir.