It's not because we don't trust people's searching skills to find previously reported bugs. We like to look at them first, because so many users think they have found a bug, when really they just haven't learned how to use the program. In my experience, I'd estimate 8 out of 10 messages where people think they found a bug, turn out they just haven't learned how to do something correctly. Or sometimes the problem is not where they thought it was, or well, in general, it cuts down on work by the bug managers, if we can sort of filter out some of the noise.
Hhm, this one is a bit over my head. On the surface, I agree that it does look buggish. But you still have the scale problem in the file, that I mentioned to you in your other topic.
Fixing the scale problem changes the inline parameters. And after that, changing the width seems to work as expected.
But XML in general, and the XML Editor specifically are a little too far over my head, for me to be able to say whether the problem you see is related to the incorrect scale, or if there's something else affecting the issue. If I understand you correctly, the "Line" object (which afaik, Inkscape can't create) is a result of a script which you used on a file from another program? So there could be something about that, which is serving as the "wrench" in the works (as they say).
Or it could be yet something else affecting it. For example, if I don't fix the scale first, and I follow your steps to change the width in the XML Editor, yes, I do see the problem. But if I Undo it, on the canvas, the width suddenly changes! Even though the XML Editor still shows the original width, the line on the canvas becomes huge, and is reported on the canvas as 10 (even though undoing should have put it back to the original
)
So there is something funky going on, somewhere. But much of it is beyond my abilities to pinpoint.
Are you able to fix the scale issue before you paste in the XML? That would be a good first step to narrow it down.
Also, someone else should be along, before too long, who either might know somthing about whether it's been reported, or would have the right skills to sort out exactly where the problem is.
(Regarding searching, the Launchpad search is known to be horrible. I can search on words that I know I wrote in a bug title, in LP, and not find the report! We are still fairly new at using gitlab for a bug tracker, so it's not clear how well it's able to search. So far, so good, but it doesn't have 5000 reports yet, so time will tell. But LP is definitely hard to search!)
