[sylpheed:36766] Re: Strange bug with small screen
stefan at capable.ca
Sun Jan 27 03:29:40 JST 2019
I haven't had a chance to look at this for a while, but have an interesting
new finding. The other day I pulled out my Debian 8 Intel laptop, updated it,
and now the bug is happening there too. I wonder if a bug has been recently
introduced into GTK, and doing an 'apt-get update' installed the buggy version?
On Wed, 26 Dec 2018 21:14:12 -0500
Michael Shell <list1 at michaelshell.org> wrote:
> On Wed, 26 Dec 2018 10:03:53 -0500
> Stefan Vorkoetter <stefan at capable.ca> wrote:
> > I tried that, and it does stop the crash. Strangely enough,
> > signature handling still works though (i.e. I can select from
> > between my two accounts and the appropriate signature appears at
> > the bottom of the message). Maybe I'm misunderstanding what you
> > mean by "signature handling", since clearly that loop will not
> > executed when valid is zero.
> I think that loop updates the signature *menu* which is the list of
> signatures we can select from shown to the right of the From: menu
> in the compose window. I think.
> It seems compose->account->sig_names does not point to valid
> memory, i.e., has not been allocated.
> > I'm not sure I have an old enough backup of it anywhere.
> Well, perhaps you can start with an empty config dir and then manually
> reenter the server settings etc. Be sure and make/retain a copy of
> this "bare" config directory.
> If you start with a bare config directory, then set things up the
> best you can manually, then do you have a working system?
> The idea is to make incremental changes until you home in on the
> offending config change that triggers the problem.
> To me, that approach is easier than back tracking in the code
> to find where compose->account->sig_names is initialized
> (and to determine why it is not being initialized - due to
> something strange in the config file).
More information about the Sylpheed