On Fri, Dec 07, 2001 at 09:16:55PM +, Philip Blundell wrote:
> So what's the status on this now? Is anybody still suffering from the
> "flashing screen" syndrome, or has that finally been laid to rest?
>
> Jordi, did changing to the non-utf8 libraries fix your problem with the
> Catalan disk
On Fri, 07 Dec 2001 21:16:55 +
Philip Blundell <[EMAIL PROTECTED]> wrote:
> So what's the status on this now? Is anybody still suffering from the
> "flashing screen" syndrome, or has that finally been laid to rest?
I've checked the boot-floppies on ~aph, from 6 Dec, and
it seems to be work
So what's the status on this now? Is anybody still suffering from the
"flashing screen" syndrome, or has that finally been laid to rest?
Jordi, did changing to the non-utf8 libraries fix your problem with the
Catalan disks?
p.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "
In message <[EMAIL PROTECTED]>, Adam Di Carlo writes:
>Ah! We should check for this in make check what should that link
>be pointing to ?
I think it says in the bug report. Something like libnewt.so.0.50 from what I
remember. It's probably good enough just to check that it points to a fil
On Thu, Dec 06, 2001 at 02:25:41PM -0500, Adam Di Carlo wrote:
> Philip Blundell <[EMAIL PROTECTED]> writes:
> > #121893 is still outstanding, and would cause these symptoms. Check your
> > symlink is correct.
> Ah! We should check for this in make check what should that link
> be pointing t
In message <[EMAIL PROTECTED]>, Adam Di Carlo writes:
>No I get the same thing. This is definately blocking.
>
>I think I may have to turn off i18n to get this working again. Or else
>is there any fix for this? Wasn't this the libnewt issue?
#121893 is still outstanding, and would cause these s
6 matches
Mail list logo