[sylpheed:36758] Re: Strange bug with small screen
stefan at capable.ca
Wed Dec 19 21:40:24 JST 2018
On Wed, 19 Dec 2018 02:09:43 -0500
Michael Shell <list1 at michaelshell.org> wrote:
> On Tue, 18 Dec 2018 09:05:05 -0500
> Stefan Vorkoetter <stefan at capable.ca> wrote:
> > However, I recently logged into the tablet remotely from my
> > desktop, and launched Sylpheed from there so that it opened on my
> > desktop machine. That also worked fine.
> > However, ever since then, if I launch Sylpheed from the taskbar
> > icon on the tablet, and then tap anything that opens another
> > Sylpheed window (e.g. compose a message, preferences, etc.) it
> > immediately crashes and closes.
> It would seem that a problematic change occurred in your .sylpheed-2.0
> dir and that is triggering the problem (how else would sylpheed
> "know/remember" that it had been run remotely?). I would save a copy
> of that dir and then start deleting the cache files, etc. to see if
> the problem can be overcome. (Or even start with an
> empty .sylpheed-2.0 to see if that allows other windows to open OK.)
Indeed. My feeling is that it's somehow remembering a window size, which is too big to fit on the screen, which in turn is triggering a bug, causing the crash (windows that are too big to fit shouldn't normally crash a program).
> Also, I would want to know exactly how the tablet taskbar is lauching
> sylpheed - what is the exact command it calls?
The .desktop file is just launching "sylpheed %u".
> But, for the ultimate investigation, sylpheed should be started under
> the gbd debugger so that you can do a backtrace and see where exactly
> in the code the crash happens.
> With a shell, you would do:
> gdb sylpheed
> but, you would have to find a way to feed the run and bt commands
> to gbd (as well as see the response to them) under a taskbar launch.
I hadn't thought of using gdb on it. The easiest way would be to launch sylpheed, and then attach gdb to the running process. I do that all the time for the stuff I work on at work. I'll just need to build a debug (compiled with -g) version of Sylpheed (in which the problem hopefully still occurs).
More information about the Sylpheed