Bug 491252
Summary: | The function of "Check for new articles every "number" minutes for newsgroup" does not work. | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Yewei Shao <mshao> |
Component: | thunderbird | Assignee: | Jan Horak <jhorak> |
Status: | CLOSED UPSTREAM | QA Contact: | desktop-bugs <desktop-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 5.3 | ||
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-04-08 15:05:31 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Yewei Shao
2009-03-20 03:08:52 UTC
Could you reproduce it with RHEL5, please? I don't think we will fix this for RHEL4. It can be reproduced in RHEL5. yup, even after half an hour (with 1 minute set as the time limit) anything happened. And actually, even though newsgroups GET the messages when you click on Get New Messages, folders are not made bold and no number of new messages is shown, until one clicks on the particular folder. We found this bug in the upstream database (https://bugzilla.mozilla.org/show_bug.cgi?id=303526) and believe that it is more appropriate to let it be resolved upstream. Red Hat will continue to track the issue in the centralized upstream bug tracker, and will review any bug fixes that become available for consideration in future updates. Thank you for the bug report. And, no, restart of TB (as suggested in https://bugzilla.mozilla.org/show_bug.cgi?id=24594) didn't help. Second problem described in comment 4 is https://bugzilla.mozilla.org/show_bug.cgi?id=260545 (In reply to comment #5) > And, no, restart of TB (as suggested in > https://bugzilla.mozilla.org/show_bug.cgi?id=24594) didn't help. Taking back ... it did help and new messages are now arriving. Restart of TB is all what's needed. So this is duplicate of https://bugzilla.mozilla.org/show_bug.cgi?id=24594 |