Hi Denis,

First, thanks for the reply, as I was unsure if my emails were reaching the
list.

On Dec 3, 2007 1:34 PM, Denis Oliver Kropp <[EMAIL PROTECTED]> wrote:

> John Miskinis wrote:
> > Hi Folks,
> >
> > I've been using directfb along with GTK+ for a couple months, and I've
> > been ignoring the "fusion call return" errors until now.  I am referring
> > to the messages such as:
> >
> > (!) FUSION_CALL_RETURN    --> Input/output error
>
> Which versions of DirectFB, GTK+ and especially linux-fusion are you
> using?


We are currently using DirectFB components:
linux-fusion-3.2.4  DirectFB-1.0.0  DFBTerm-0.8.15  LiTE-0.8.3

We are currently using GTK+ components:
atk-1.10.3  cairo-1.2.4  fontconfig-2.3.93  freetype-2.1.9  glib-2.12.0
gtk+-2.10.1  libpng-1.2.10  libxml2-2.6.23  pango-1.14.0  zlib-1.2.3

We are building and running on Fedora Core 7, using kernel 2.6.22.9-91.fc7

We apply a small patch to gtk+2.10.1 that was developed by some folks
that were trying to port the firefox2 browser to GTK+/DirectFB, which
appears
to correct some issues regarding an assertion and some color issues.

We dropped back to GTK+ 2.10.1 (with patch) recently, from the 2.10.13
that we were using, to be consistent with some other developers on our
team.

But, we have always seen these fusion call return errors on every machine
and
every version of GTK+ (and deps) and DirectFB combination we have tried.
We have not yet experimented with the 1.1.0 (latest?) DirectFB however.

>
> > It seems that even when running the GTK+ examples under DFB, such as
> > "helloworld2", that these messages are also displayed.
> >
> > The time has come for me to understand:
> >
> > 1 - Why they are happening
>
> In the latest code it indicates FUSION_CALL_RETURN being called twice
> for the same call instance.
>
> > 2 - Can they be stopped or corrected
> > 3 - If they have any ill side effects at all
>
> If it still appears with latest versions, there's something really broken
> and should be addressed.
>

Thaks for confirming that the error messages are indeed indicating that
something is
really wrong.  I can try out the latest (1.1.0?) DirectFB later this week,
to see if the errors
vanish.  Perhaps whatever *is* wrong here, is also contributing to the
machine freeze-ups
that we see about twice-per-day on average.

>
> --
> Best regards,
>  Denis Oliver Kropp
>
> .------------------------------------------.
> | DirectFB - Hardware accelerated graphics |
> | http://www.directfb.org/                 |
> "------------------------------------------"
>
_______________________________________________
directfb-dev mailing list
directfb-dev@directfb.org
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev

Reply via email to