On Thu, 13 Aug 2020 at 19:31:38 +0200, Francesco Poli wrote: > On Thu, 13 Aug 2020 09:20:30 +0100 Matthew Munro <bugzilla...@gmail.com> > wrote: > > Following libpango-1.0-0 (and others) upgrade this morning, gdb reports: > > > > Thread 1 "sylpheed" received signal SIGSEGV, Segmentation fault. > > 0xb73cfebf in pango_renderer_part_changed () > > from /usr/lib/i386-linux-gnu/libpango-1.0.so.0
If this isn't immediately reproducible in an unconfigured copy of sylpheed (I haven't tried yet, I don't use it myself), then we'll need more information than this to be able to diagnose what's happening. Please quote the whole backtrace, preferably after installing debugging symbols for pango, sylpheed and any other libraries that show up in the backtrace. More information on detached debug symbols and getting a backtrace: https://wiki.debian.org/HowToGetABacktrace > I do not know whether a fix is needed in sylpheed or in libpango-1.0-0, > but a RC bug report against libpango-1.0-0 is necessary in order to > prevent its migration to testing. My understanding had been that the preferred representation for that is to reassign the bug to *both* packages ("reassign -1 libpango-1.0-0,sylpheed", "found -1 pango1.0/x.y.z", "found -1 sylpheed/u.v.w"), which avoids having to either duplicate relevant information between the two bugs, or have the information only show up in one of the two places. Thanks, smcv
