On Thu, Nov 26, 2015 at 09:00:22AM +0530, Sebastian Dröge wrote: > On Sa, 2015-11-21 at 17:06 +0100, Agustin Martin wrote: > > 2015-11-14 15:25 GMT+01:00 Soeren D. Schulze <soeren.d.schu...@gmx.de > > >: > > > I am not sure about those SIGPIPEs. They occured to me, too, but I > > > could > > > just press 'c' in gdb and continue using iceweasel until the > > > SIGSEGV. On > > > the other hand, they are apparently gone now in stretch. > > > > > > Could you press 'c' next time it happens, and wait for a SIGSEGV to > > > occur? > > > > Hi, > > > > This time a SIGSEV did occur, please find attached backtrace > > Hi, > > this is a completely different crash than the one related to faad that > was fixed in sid.
Hi, thanks, for the info I am remembering more about the original faad issue and failure was indeed really inmediate when entering some pages. Not what is hapening in this box. > Do you have a way to reproduce the crash you're > observing here? Unfortunately not, I could not find a reproducible path to the problem, once happened with facebook (at that time it looked reproducible, but when looking next day at the entries apparently problmatic, everything went fine), sometimes happens when accesing online journals, but is by far not as inmediate as it happened with the faad issue. When this problem happens I am already browsing the page after entering it. I will open a new bug report if I can find a reproducibility path. In the mean time I think original gstreamer1.0-plugins-bad can be left for natural archiving. Regards, amd thaks again for all the feedback. -- Agustin
