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 615782 - Delete messages in Search Folder ... Do not ask me again: not working
Delete messages in Search Folder ... Do not ask me again: not working
Status: RESOLVED DUPLICATE of bug 620628
Product: evolution
Classification: Applications
Component: Mailer
2.30.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
evolution[vfolders]
Depends on:
Blocks:
 
 
Reported: 2010-04-14 20:35 UTC by Brian J. Murrell
Modified: 2010-06-13 23:02 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Brian J. Murrell 2010-04-14 20:35:55 UTC 
If I delete a message while reading a search folder I get a dialog warning me that the message will be deleted in from a real folder and it gives me a typical "Do not ask me again" checkbox, which I check, yet the very next message I delete pops up the same dialog.
Comment 1 Brian J. Murrell 2010-04-14 20:38:24 UTC 
Strangely, it's now not popping up the dialog.

I most definitely did get it a number of times and did select the "Do not ask me again" checkbox.
Comment 2 Akhil Laddha 2010-04-15 04:32:56 UTC 
I don't get warning at all in my evolution 2.31.1 build.
Comment 3 Olivier Berger 2010-06-13 21:28:23 UTC 
(In reply to comment #0)
> If I delete a message while reading a search folder I get a dialog warning me
> that the message will be deleted in from a real folder and it gives me a
> typical "Do not ask me again" checkbox, which I check, yet the very next
> message I delete pops up the same dialog.

I do confirm this with Evo 2.30.1.2 in Debian (see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=585794 for my report in Debian's bugtracker).
Comment 4 Matthew Barnes 2010-06-13 23:02:26 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 620628 ***