From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: From: Juergen Beisert Date: Thu, 26 Jan 2012 13:50:00 +0100 References: <201201261132.17940.jbe@pengutronix.de> In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Message-Id: <201201261350.00935.jbe@pengutronix.de> Subject: Re: [ptxdist] [oselas] GTK+ on DirectFB Reply-To: ptxdist@pengutronix.de List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: ptxdist-bounces@pengutronix.de Errors-To: ptxdist-bounces@pengutronix.de To: oselas@community.pengutronix.de Cc: ptxdist@pengutronix.de, Guillermo Rodriguez Garcia Hi Guillermo, Guillermo Rodriguez Garcia wrote: > 2012/1/26 Juergen Beisert : > > Hi Guillermo, > > > > Guillermo Rodriguez Garcia wrote: > >> [...] > >> (testgtk:739): Gdk-CRITICAL **: IA__gdk_drawable_set_colormap: > >> assertion `cmap =3D=3D NULL || gdk_drawable_get_depth (drawable) =3D= =3D cmd > >> (*) Direct/Thread: Started 'EventBufferFeed' (-1) [MESSAGING > >> OTHER/OTHER 0/0] <8388608>... > >> (!) [ =A0739: =A0 =A00.000] --> Caught signal 11 (at 0x28, invalid add= ress) > >> <-- > >> =A0(!!!) =A0*** WARNING [still objects in 'Window Pool'] *** [object.c= :241 > >> in fusion_object_pool_destroy()] (!!!) =A0*** WARNING [still objects in > >> 'Layer Region Pool'] *** > >> [object.c:241 in fusion_object_pool_destroy()] > >> =A0(!!!) =A0*** WARNING [still objects in 'Layer Context Pool'] *** > >> [object.c:241 in fusion_object_pool_destroy()] > >> =A0(!!!) =A0*** WARNING [still objects in 'Surface Pool'] *** > >> [object.c:241 in fusion_object_pool_destroy()] > >> Aborted > >> > >> Can anyone share any experiences on this? > > > > Did you re-start with a clean GTK after you switch from Xorg to DirectF= B? > > Sometimes the package's buildsystem does not re-compile everything after > > changing some parameters, so some object files are still compiled for t= he > > previous parameter settings. Just an idea. > > No, I didn't. I assumed ptxdist would take care. PTXdist: yes. It calls again the package's configure script with the new = settings. But sometimes the package's buildsystem is broken and it does not = re-compile all objects in accordance to the new configuration. > I'll give this a shot, rebuilding everything from scratch. Not everything: a "ptxdist clean gtk" should be enough. This means only the = gtk package starts from scratch. Regards, Juergen -- = Pengutronix e.K. | Juergen Beisert = | Linux Solutions for Science and Industry | http://www.pengutronix.de/ = | -- = ptxdist mailing list ptxdist@pengutronix.de