Bug 1480021 - Default mail account not indicated after restart
Default mail account not indicated after restart
Status: CLOSED NEXTRELEASE
Product: Fedora
Classification: Fedora
Component: evolution (Show other bugs)
26
x86_64 Linux
unspecified Severity medium
: ---
: ---
Assigned To: Milan Crha
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-08-09 20:10 EDT by Luigi Cantoni
Modified: 2017-08-22 04:12 EDT (History)
2 users (show)

See Also:
Fixed In Version: evolution-3.25.92
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-08-22 04:12:16 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Luigi Cantoni 2017-08-09 20:10:09 EDT
Description of problem:
Default account marked but after close and re-open evolution not account marked as default

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

How reproducible:
Yes

Steps to Reproduce:
1. set an account as default.
2. Close evolution
3. restart and no account is marked

Actual results:
no account marked as default

Expected results:
Account should be marked as default

Additional info:
I am sure this problem happened several OS versions ago and has come back again
Comment 1 Milan Crha 2017-08-22 04:12:16 EDT
Thanks for a bug report. Using GNOME bugzilla for non-Fedora related issues is appreciated, but I understand that users do not have accounts in all bug trackers out there, thus no big deal.

I fixed it with the below change. It had been still set, but the underlying structure didn't have it properly populated, thus Edit->Preferences->Mail Accounts didn't indicate the account as default.

Created commit e4ee99b in evo master (3.25.92+) [1]

[1] https://git.gnome.org/browse/evolution/commit/?id=e4ee99b

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