Bug 1177392 - evolution no longer returns to previous email upon start
Summary: evolution no longer returns to previous email upon start
Keywords:
Status: CLOSED DUPLICATE of bug 1176520
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 21
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Milan Crha
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-12-26 21:39 UTC by Christian Lupien
Modified: 2015-01-06 08:34 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-01-06 08:34:25 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Christian Lupien 2014-12-26 21:39:12 UTC
Description of problem:
When starting evolution, it no longers resume to the email which was last seen before shutdown. This used to work under fedora 20.

Version-Release number of selected component (if applicable):
evolution-3.12.9-1.fc21.x86_64

How reproducible:
Always

Steps to Reproduce:
1.Within evolution, select an email so that you see its preview
2.Quit evolution
3.Restart evolution

Actual results:
No email is selected upon restart, the preview is blank and the list of emails is at the top.

Expected results:
The last email seen should be the selected one upon restart.

Additional info:
After restart, before selecting any email, just switching to another folder and then back will select the previous (before shutdown) email. So the information is available, it is just not acted upon when starting evolution. However it works when the user switches folders.

Comment 1 Milan Crha 2015-01-06 08:34:25 UTC
Thanks for a bug report. This particular one had been reported already, thus I'm marking it as a duplicate.

I was able to reproduce this before Christmas, but currently I cannot for some reason. I will use your information to focus my reproducer finding to.

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


Note You need to log in before you can comment on or make changes to this bug.