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 552771 - Outbox misbehaves
Outbox misbehaves
Status: RESOLVED WONTFIX
Product: evolution
Classification: Applications
Component: Mailer
2.24.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
evolution[disk-summary]
Depends on:
Blocks: 543389
 
 
Reported: 2008-09-18 13:13 UTC by Milan Crha
Modified: 2009-01-29 17:59 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Milan Crha 2008-09-18 13:13:26 UTC
I noticed some strangeness of behaving of Outbox. See the steps:
a) go to offline in mail component
b) clove evo family *
c) run evolution on console
d) go to contacts component (I use buttons on the left here)
e) on one contact with mail filled do "Send Message to Contact"
f) fill something there and hit send
g) close evo family *
h) run evolution on console (still in contacts)
i) with other email-capable contact "Send Message to Contact"
j) go to mail component (again with button on the left bottom)

*) by "close evo family" I mean:
   1) close evolution
   2) invoke evolution --force-shutdown to close eds and other too

Actual results:
Local Outbox in tree shows (2), but only 1 message is shown in the list

Expected results:
See both messages on a first hit. The only way I found how to show the second message was to delete the first. And it also sometimes works and sometimes not. But definitely related to this, thus let it be for now.
Comment 1 Srinivasa Ragavan 2009-01-29 16:54:58 UTC
One point, we don't guarantee of cache, when you pkill :-)

evolution --force-shutdown actually does pkill. 

Wont-fix. Get me this without pkill to fix ;-)
Comment 2 Milan Crha 2009-01-29 17:59:27 UTC
I thought, when you *close evolution*, and *then* --force-shutdown it should work, because all that holds is nothing related to camel and mail cache, thus should be fine. Am I wrong?