public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] gdk-pixbuf-query-loaders usage in tree
Date: Tue, 18 Oct 2011 20:21:32 +0200	[thread overview]
Message-ID: <1318962092.21882.1.camel@belkin4> (raw)
In-Reply-To: <CAN3AtvqatuOaAJojBXpYsSkBitTiJWm+bC1r8CpQP7cB7ypx7A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1217 bytes --]

El dom, 09-10-2011 a las 10:48 +0200, Fabio Erculiani escribió:
> gdk-pixbuf-query-loaders has a long history of segfaults.
> Not to blame anybody here, but still segfaults there can happen quite easily.
> 
> A nice example is:
> export __GL_NO_DSO_FINALIZER=1
> $ gdk-pixbuf-query-loaders
> When nvidia.ko is in use.
> 
> The __GL_NO_DSO_FINALIZER is a hack that made buggy nvidia-drivers (or
> buggy gl threads usage?) work.
> The problem with our ebuilds is that everybody did something like this
> (in pkg_postinst):
> 
> gdk-pixbuf-query-loaders > "${ROOT}usr/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache"
> 
> 1) exit status is not even considered
> 2) output redirection truncates the destination file as soon as the
> executable is spawned
> 
> This is very bad, because in case of segfaults, loaders.cache is
> totalled, resulting in gtk+ apps dying miserably.
> 
> Please don't do that, never ever. We don't live in a perfect world.
> 
> x11-libs/gdk-pixbuf got fixed already.
> 
> Others affected:
> app-emulation/emul-linux-x86-gtklibs
> gnome-base/librsvg
> media-libs/libwmf
> others?
> 

I would really appreciate if you could fix this three yourself :-)

Thanks a lot

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

      reply	other threads:[~2011-10-18 18:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-09  8:48 [gentoo-dev] gdk-pixbuf-query-loaders usage in tree Fabio Erculiani
2011-10-18 18:21 ` Pacho Ramos [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1318962092.21882.1.camel@belkin4 \
    --to=pacho@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox