Re: Two problems with new FC3 x86_64 install

On 12/28/2004 11:05:03 AM, Pawel Salek wrote:
On 12/27/2004 10:26:17 PM, Willem Riede wrote:
>  I'm upgrading to an Athlon 64 PC running FC3 x86_64. I compiled
> balsa  2.2.6   for that architecture. I'm running dovecot as the IMAP
> server on the  same   machine, and selected Maildir format this time
> (my old PC uses mbox,  so this   is a new experience for me).
> I now see two issues:
> 1. Balsa's process hangs around indefinitely after quit.
> 0   500  7173     1  15   0 192660 35200 184467 S  ?          0:13
> balsa
> [wriede backup ~]$ strace -p 7173
> Process 7173 attached - interrupt to quit
> futex(0x390a52e620, FUTEX_WAIT, 2, NULL
> Google tells me that something similar has been reported before:
> (,
> but I can't find if it has been resolved, or what the fix is if it
> has...

Have you got all the glibc updates? I have tested balsa-2.2.6 on
exactly the same hardware (even SMP) + IMAP (but without POP3) and with
current glibc it works just fine.

[root backup etc]# rpm -qa --queryformat "%20{name} %{version}-%{release} % {arch}\n" 'glibc*'
       glibc-common  2.3.4-2.fc3  x86_64
      glibc-headers  2.3.4-2.fc3  x86_64
  glibc-kernheaders  2.4-9.1.87  x86_64
              glibc  2.3.4-2.fc3  x86_64
        glibc-devel  2.3.4-2.fc3  x86_64
              glibc  2.3.4-2.fc3  i686

Yum doesn't show any available updates (because I used it earlier to get all available updates...).

Which kernel are (or were) you running - your question made me realize that I hadn't yet rebooted to run the latest kernel update (2.6.9-1.681_FC3). More Googling has just revealed that Andrew Morton has a futex_wait-fix.patch in 2.6.10-rc1-mm5, which most likely our Fedora friends put in the latest rpm.

Anyway, the good news is, that balsa now exits properly. Can you try that too, since I see from your second mail you've reproduced the problem?

> 2. I deliver mail with procmail to Maildir folders, new messages get
> delivered
> to for exampe ~/Maildir/.Test/new, but don't get noticed by balsa
> until Test gets re-opened. Is that normal?

No, it is not. I assume that clicking "check" does not make balsa
discover them? And the periodic checking does not discover them either?

Indeed, none of those discover the new messages.

I believe that even opening another message from the same folder should
have the same effect of checking the folder for new messages. In any
case balsa may not discover that instantly. We might be using something
like libgamin for this (with all its tradeoffs).

So I read a couple of messages in an IMAP box that is known to have as yet undiscovered new messages, and balsa didn't find the new ones then either :-(

What can I do to help debug this (as this behavior didn't change with the kernel update)?

Regards, Willem Riede.

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]