Using standard and then custom page size saved it into the printing.ini
with keys related to standard page size and the print dialog preferred
the standard size over the custom. Removing the group from the key file
first makes this work properly. Do the same for printer settings.
Also allow changing page size in the print dialog, but do not save it.
Using CAMEL_DEBUG=message-list will print how many messages had been
reported by the selected folder and what expression had been used
to generate the list of messages.
When changing start time after end or end time before start, the other
time had been modified to be one hour duration. This change uses the original
duration instead, if possible.
Reported downstream at:
https://bugzilla.redhat.com/show_bug.cgi?id=1480029
This avoids scrolling, thus make sit easier to pick a time from
the offered list of available times. It can still show only one
column, when the list of available times is not divisible by
any predefined value.
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.
Reported downstream at:
https://bugzilla.redhat.com/show_bug.cgi?id=1480021
These are marked as incomplete, because the SRV record contains only
host name and port, thus all the other values being set are just a guess.
The change also makes prefer complete lookup results over those incomplete.
An Exchange server, eventually also a GroupWise server, can break a GPG
encrypted message structure by changing it from
multipart/encrypted; protocol="application/pgp-encrypted"
application/pgp-encrypted
application/octet-stream; name="encrypted.asc"
to something like:
multipart/mixed
text/plain
application/pgp-encrypted; name="ATT00001"
application/octet-stream; name="encrypted.asc"
where the text/plain part is empty and is added by the Exchange server.
The added code tries to detect such issues and if recognized, then
changes the structure to be able to decrypt the message as expected.
Most of the EAlertSink implementors use EAlertBar to present those
alerts and all of these had almost identical code to deal with it.
The added function is for these implementations to share the code.
Right-click and create new event or task already derives the calendar/task
list of the selected component. This derives also selected date, thus for
example creating a new event and right-clicking on the 'Tomorrow' row
the event will be prefilled with the Tomorrow date and the nearest
future time of the current time according to set time division for
the Day and Work Week views.
That was a memory leak, but apart of that it could also cause use-after-free
crash in gtk_widget_get_scale_factor() under _gtk_style_cascade_add_provider()
called from shell_window_constructed(), when creating a new shell window
for the second time, with the previous one already closed.
Milan Crha