Although prior fix for bug #737811 solved problem for some users,
apparently Geary still had an issue when upgrading a database with
new GLib Mutex implementation, which uses Linux's futexes whenever
available. This solution gives the notifying thread a chance to
signal the waiter that its work is completed.
This also closes bug #713808, as lesser-used fields (Reply-To, Bcc)
are hidden unless the user expands the composer to show them. Right
now that is an option in the composer's toolbar menu; that may change
in the future if we can find the right place to put the widgetry.
Geary can now be configured to notify of new mail at startup. When
the user logs in, Geary will autostart with a hidden window and
notify of new mail as usual. When Geary is formally executed by
the user the Geary window simply appears.
In this mode, if the user closes the window Geary will return to its
hidden state. Quit must be used to close the process.
User may now add a brief signature in the Accounts manager for
each account. When starting a new message or replying, the signature
is prepended to the edit text.
Certificate verification was failing because the wrong Connectable
was being passed to the TLS connection code. This patch also cleans
up Geary.Endpoint by using a NetworkAddress object to hold the
hostname and port.
Technically broken (unencoded dot!) "From:" addresses like
=?utf-8?Q?WestLicht.=20Schauplatz=20f=C3=BCr=20Fotografie?= <info@westlicht.com>
were not decoded in Geary's conversation viewer.
Other clients like Gmail and Thunderbird handle the
brokenness, and we should too.
This also closes bgo#714339, "subject contains garbled UTF-8
characters".
https://bugzilla.gnome.org/show_bug.cgi?id=713060https://bugzilla.gnome.org/show_bug.cgi?id=714339
Some themes (elementary's, Mint 16's Cinnamon theme) cause the
conversation list to appear squished. It has to do with how the
conversation list calculates the size of each element at app
startup.
This doesn't solve #6205, as other unknown responses can cause this
problem as well, but it does fix this for the most-commonly reported
cause of this issue, MYRIGHTS.
