[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: pango_layout_iter_next_char: Now is the time?



Hello Owen,

> A) Generally, bug fixes for particular upstream
>    packages are best discussed in the appropriate upstream forum.

Well, I attend a few upstream fora, but I do not intend to attend all
fora for packages I have an issue with.

> B) "Please fix this bug" mails are virtually never useful

I thought I'd give it a try anyway.

> C) Your Pango problem was fixed long ago. The Pango bug is still 
>    open because there are deeper/harder issues that also need
>    to be fixed.

Fixed? I just recreated that crash. Or am I interpreting the following
incorrectly?:

#3  <signal handler called>
#4  0x00aa8548 in pango_layout_iter_get_char_extents ()
   from /usr/lib/libpango-1.0.so.0

Are you sure we are speaking of the same issue? If it was fixed then
where, when and how was it fixed?

Are you telling me the "major amount of work" you mention in
http://bugzilla.gnome.org/show_bug.cgi?id=89541 has already been done?

> D) Your other issues have nothing to do with Pango. 
>    (E.g., the crash you were getting was because the title
>    of the terminal tab was being set to junk characters by
>    MC. Now that the Pango crash is fixed, you see the
>    junk characters...)

No. I've always seen the junk characters. I really believe you are
referring to a different issue. Please check the bug reports for details
to make sure we are speaking of the same issue.

Leonard.

-- 
mount -t life -o ro /dev/dna /genetic/research




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]