Hi, On Tue, 2010-02-09 at 09:55 +0100, Steffen Bretschneider wrote: > The first start works pretty well and I get the following output:
it seems you are using two different gfxdrivers: > (!) Direct/Modules: Module 'libdirectfb_stblit_accel.so' did not register > itself > after loading! Trying default module constructor... > (!) DirectFB/gfxdrivers/dfb_stblit_accel: FB file descriptor = 27 > (*) DirectFB/Graphics: ST Microelectronics STAPI Blit based graphic > acceleration > 0.1 (ST Microelectronics) the STAPI one (which works with the STAPI framebuffer driver) on your first start... > But the second run tells me that it could not initialize the screen. > [...] > (*) DirectFB/gfxdrivers/stgfx: FB file descriptor = 27 > (*) DirectFB/Graphics: ST Microelectronics Gamma 1.0 (ST Microelectronics) ... and the one from STLinux on the second. How have you managed to do that? How are you restarting DirectFB? I mean, do you start your app twice, or do you DirectFBCreate() inside your app multiple times? As a side note in case it's the latter, there will still be some mem leaks even if you release all surfaces etc. Since you are a STAPI user I believe, please make sure you delete the /usr/lib/directfb-1.0-0/libdirectfb_stgfx*.so files. They should not be there in the first place. (You can always reinstall them by reinstalling the directfb rpm, but the stgfx* drivers only work with the STLinux stmfb framebuffer driver) HTH, Andre' _______________________________________________ directfb-users mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
