Is anyone else having problems with the new gnus agent code?

Is anyone else having problems with the new gnus agent code?

[Barry Fishman]

Since the last major change in the CVS agent code (2004-04-07) I have
had problems with the stable tracking of messages read.  I'm running
SuSE Linux 9.1 with CVS gnus and CVS emacs.

The most evident problem was with not seeing changes made while
reading news offline:

   a) Start emacs, run gnus (online) do a "J s".  Exit gnus. Exit
      emacs.

   b) Start emacs, run gnus (offline). Read news. Exit gnus Exit emacs.

   c) Start emacs, run gnus (online).  Read news shows up as unread.
      Exit gnus.  Exit emacs.

The proposed solution was to set gnus-agent-syncronize-flags to t.
(Which i do in the ~/.gnus file, along with (require 'gnus-load) done
in my ~/.emacs file.

Afterwards I saw no difference when doing the precedure shown above.
However, if I repeat step c, the read messages seem marked correctly.

However, performing the following gives strange results.

   d) Start emacs, run gnus (online). Do the following in a group:
        "ESC c"   mark all message unread.
        "c y"     catch up group.
        "G E"     edit group.  Decrease last read message number by
                  40.
      The number of unread messages is 40.  Exit gnus. Exit Emacs.

   e) Start emacs run gnus (online).  The number of unread in the
      previous group is 0 or some small value (the number of new
      messages?).
                  
Repeating step e does not change anything.

Is this true for anyone else?  My gnus setup is a bit envolved, but It
may be unusual in that everything is set with lisp code in .emacs and
.gnus, rather than using customize.  The ownly agent related code
is in ~/.gnus:

;;; Now set in cateogry file (but doesn't seem to work there)
(setf gnus-agent-expire-days 0)
(setf gnus-agent-short-article 250)

;;; Keep offline changes
(setf gnus-agent-synchronize-flags t)

-- 
Barry Fishman