After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 128154 - Untoggle "Match New Headers" toobar button fails after reloading filtered group
Untoggle "Match New Headers" toobar button fails after reloading filtered group
Status: RESOLVED FIXED
Product: Pan
Classification: Other
Component: general
0.14.2.90
Other Linux
: Normal minor
: 0.14.3
Assigned To: Charles Kerr
Pan QA Team
: 143253 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2003-11-29 01:51 UTC by subscriptions
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description subscriptions 2003-11-29 01:51:24 UTC
Problem: 
After toggling on a group's "Show only new articles" filter from the
toolbar button, switching to another group, then returning, clicking the
toolbar button again will change its visual state to unpressed, but will
not untoggle "Show only new articles".  "Filter->Match New Articles" from
the menu will fix this.

Procedure:
1) Choose any group and download new headers.
2) Press the "Show Only New Articles" toolbar button to toggle the "New
Article" filter on.
3) Choose any other group and download headers.
4) Switch back to the group selected in (1).
5) Press the (now active) "Show Only New Articles" toolbar button to
untoggle.  The visual state of the button changes to off, but the display
of articles does not change.
Comment 1 Charles Kerr 2003-11-29 03:08:32 UTC
Fixed in 0.14.2.90

*** This bug has been marked as a duplicate of 120129 ***
Comment 2 Charles Kerr 2003-11-29 03:20:16 UTC
no, no, this isn't a duplicate of 120129, sorry.
should've read more closely.
Comment 3 Charles Kerr 2003-11-29 03:27:20 UTC
Confirmed.  This is a new bug made by the changes made for #120129.
Comment 5 subscriptions 2003-11-30 01:52:01 UTC
That does appear to fix it.  Thank you.


Comment 6 Christophe Lambin 2004-05-29 10:14:22 UTC
*** Bug 143253 has been marked as a duplicate of this bug. ***