public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: felix@crowfix.com
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] FVWM taskbar segfault on ~amd64
Date: Thu, 28 Feb 2008 00:33:11 -0800	[thread overview]
Message-ID: <20080228083311.GA10197@crowfix.com> (raw)
In-Reply-To: <20080221230050.GA10216@crowfix.com>

On Thu, Feb 21, 2008 at 03:00:50PM -0800, felix@crowfix.com wrote:
> On Thu, Feb 21, 2008 at 11:40:29PM +0100, Jes?s Guerrero wrote:
> 
> > As you see, you have many alternatives. The problem with either of this,
> > is that you are the responsible to update the ebuild when necesary via svn.
> > 
> > If you have questions, just ask.
> 
> I just may do that :-)  I will see how the new fvwm works probably
> next Wednesday, and go from there.

Well, no luck.  taskbar still segfaults:

[  165.614093] FvwmTaskBar[14701]: segfault at fffffff7 rip 2b7c4a6c52b5 rsp 7fff637048c0 error 4

[ebuild   R   ] x11-wm/fvwm-9999  USE="bidi doc gtk imlib nls perl png readline session stroke svg tk truetype xinerama xpm -debug -extras -rplay -shape -translucency" 0 kB [1]

I noticed that the fvwm overlay version is not very useful.  Mplayer,
for instance, which is also part of the devnull overlay, has a useful
version:

[ebuild   R   ] media-video/mplayer-2008.0103

fvwm --help is only slightly more useful:

fvwm 2.5.25 (from cvs) compiled on Feb 21 2008 at 20:06:03
with support for: ReadLine, Stroke, XPM, PNG, SVG, XShm, SM, Bidi text, Xinerama, XRender, XCursor, XFT, NLS

How does it track the version internally well enough to know when
updates are available?

And back to fvwm, should I report this to the gentoo maintainer (who
seems to be seriously out of date) or to the fvwm project -- does
gentoo add its own bells and whistles which would make a gentoo bug
report less useful?

-- 
            ... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._.
     Felix Finch: scarecrow repairman & rocket surgeon / felix@crowfix.com
  GPG = E987 4493 C860 246C 3B1E  6477 7838 76E9 182E 8151 ITAR license #4933
I've found a solution to Fermat's Last Theorem but I see I've run out of room o
-- 
gentoo-amd64@lists.gentoo.org mailing list



  reply	other threads:[~2008-02-28  8:33 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-21  5:24 [gentoo-amd64] FVWM taskbar segfault on ~amd64 felix
2008-02-21  5:41 ` Jesús Guerrero
2008-02-21 16:26   ` felix
2008-02-21 18:44     ` Jesús Guerrero
2008-02-21 19:04       ` felix
2008-02-21 19:42         ` Jesús Guerrero
2008-02-21 21:08           ` Sebastian Redl
2008-02-21 21:47           ` felix
2008-02-21 21:54           ` felix
2008-02-21 22:40             ` Jesús Guerrero
2008-02-21 23:00               ` felix
2008-02-28  8:33                 ` felix [this message]
2008-02-28 18:57                   ` Jesús Guerrero
2008-02-29  6:48                     ` felix
2008-02-29 14:55                       ` Jesús Guerrero
2008-02-29 17:03                         ` felix
2008-03-01  1:55                           ` [gentoo-amd64] " Duncan
2008-03-01 15:33                             ` felix

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=20080228083311.GA10197@crowfix.com \
    --to=felix@crowfix.com \
    --cc=gentoo-amd64@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