On Sat, Jul 30, 2005 at 07:59:57PM +0200, Nikolaus Rath wrote: > In principle you are right. However, in this case I felt reasonably sure > that the bug could not be caused by the Ubuntu packaging (because there > were no changes except for the rebuild). I therefore
Be wary of assuming things like this: a simple rebuild includes building against a different build environment which can produce unexpected results. > explicitly reported the bug to the debian bts. I expected this to be > helpful because it skipped yet another level between bug reporter and > upstream developer (I know that at least some leafnode developers watch Well, part of the problem here is that if you're going to do something like this you really should be explicit about what you're doing. This avoids confusion - for example, with this bug it was very puzzling to see that you were running such an old version. > Unfortunately the problem is still not solved: Some groups are empty, so > I can't read an article to subscribe to them again. Can you not read *any* articles? If so, then that is a problem. There should either be previously read articles which should be accessible via Thunderbird or (if they have all expired) a placeholder article which would show up as a new article. Have you tried opening the groups rather than just looking at the group listings? > Is there a specific reason why checking a group doesn't subscribe it? It's specifically the GROUP command that doesn't cause the group to be marked as subscribed. Listing the contents of the group or downloading an article will cause it to be marked as subscribed. This avoids false positives - for example, I believe some clients will use the GROUP command to obtain article counts when listing unsubscribed groups. -- "You grabbed my hand and we fell into it, like a daydream - or a fever." -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
