https://bugs.kde.org/show_bug.cgi?id=234778
Lays Rodrigues <laysrodriguessi...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDSINFO |RESOLVED
--- Comment #8 from Lays Rodrigues <laysrodriguessi...@gmail.com> ---
(In reply to Ralf Habacker from comment #7)
> (In reply to Lays Rodrigues from comment #6)
> > Ralf, look at the print, in the "Component view" you can see the header with
> > a broken page, and in "Logical View" the classes that were imported. So I
> > guess that this bug doesn't broke umbrello.
>
> It looks so and we can close this bug. The open question is now to which
> resolved status should we set this bug and what should we place into the
> "version fixed in" and "latest commit" field ? If this was an issue in
> version 2.4.0, it must be fixed in one of the following versions. There are
> several options to get this info:
> 1. inspect the git log
> 2. inspect the source code to find the place, where this character may be
> handled and use git log -p <file> or git blame <file> to get an idea when it
> has been fixed.
I had looked the code, and didn't find any place that the FF, \f or 0xC appear.
And if had one, I guess that doing the git log we could find something.
> 3. The issue may be fixed in a shared library umbrello depends on like
> expat, Qt or KDE base libraries
I guess that could be this.
>
> Unfortunally the original reporter did not provide a stack trace, which
> would make it much easier to find the related location.
Will you close this bug? I guess that "worksforme" could be good.
--
You are receiving this mail because:
You are watching all bug changes.
