Re: Gbd Report: emelfm2-0.8.0-1.fc16.x86_64
- From: lists@xxxxxxxxxx
- To: emelfm2@xxxxxxxxxxxxx
- Date: Fri, 6 Apr 2012 11:48:36 -0600
<.02$> dillo project switched from gtk to fltk2 a while back - i think fltk2 is
active - maybe worth looking at for emelfm2 ??? </.02$>
On Fri, 06 Apr 2012 13:07:05 -0400
xaphir <xaphir@xxxxxxxxxxxxxx> wrote:
> On 04/05/2012 02:10 AM, tpgww@xxxxxxxxxxx wrote:
> > Thanks xaphir.
> >
> > On first inspection, this looks reminiscent of some painful gtk3
> > behaviour for which a workaround has recently been implemented.
> > Evidenced by no apparent relationship between emelFM2 code and
> > reported errors.
>
> This pain is probably just beginning. The GTK is under the authority of
> the Gnome Foundation, which has plans to subsume the gnome
> libraries into the GTK toolkit; aka, Project Ridley. In my view these
> plans have a competency problem.
>
> Back when it was still the Gimp toolkit, it was a clean solution. I
> don't trust the current direction it's taking under the Gnome Foundation.
>
> >
> > In your case, the report identifies function
> > _e2_fileview_make_all_infos() which is in turn calling
> > g_slice_alloc(constant), and inside the latter there is a problem.
> > How that could possibly be related to the calling code is not at all
> > apparent.
> >
> > I propose that this be investigated further after 0.8.1 is released.
> > Or else I can post a pre-release now, if anyone wants to build and
> > test, but can't use svn code.
> >
> > Regards Tom
>
>
>
> --
> --Xaphir
> --
> °°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°
> Without a theory, the facts are silent. Without facts,
> any theory is speculation.
> Registered Linux User #268899 http://counter.li.org/
> °°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°
>
>
> --
> Users can unsubscribe from the list by sending email to
> emelfm2-request@xxxxxxxxxxxxx with 'unsubscribe' in the subject field or by
> logging into the web interface.
--
Users can unsubscribe from the list by sending email to
emelfm2-request@xxxxxxxxxxxxx with 'unsubscribe' in the subject field or by
logging into the web interface.
Other related posts:
