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 584902 - Disabled default account hides "From" in composer
Disabled default account hides "From" in composer
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Mailer
2.28.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
evolution[composer]
: 243241 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-06-05 08:34 UTC by Milan Crha
Modified: 2013-09-13 01:04 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Milan Crha 2009-06-05 08:34:49 UTC 
When I have set my default account disabled, the "From" field, with Signature, is hidden in composer, and I even cannot choose it in View menu. Actually, I cannot change anything from a View menu when the default account is disabled.
Comment 1 Matthew Barnes 2009-06-14 19:36:43 UTC 
What's happening here is when you disable your default account, highlight a folder under "On This Computer" or "Search Folders" and click "New", the mailer can't associate the selected folder with an account so it tries to fall back to the default account but can't because it's disabled.

Fixed EAccountComboBox to choose the first usable account as a last ditch fallback under these conditions, which probably won't be the account the user wants but it's the best we can do from the "widgets" level.

When opening a new composer from the mailer, we could probably be smarter about mapping the selected folder to an account.

Or we could simply prohibit the default account from being disabled and avoid this issue altogether, which is still my preference.

http://git.gnome.org/cgit/evolution/commit/?id=1276d2a9b42398e7ec978efc24e99aa6cd31e631
Comment 2 Milan Crha 2009-06-15 09:30:20 UTC 
*** Bug 243241 has been marked as a duplicate of this bug. ***