Hi Emmanuel et al, Hans Liao wrote[1]:
> Here are the segfaults I gathered from dmesg: > > [ 2419.690487] chromium[4043]: segfault at 100 ip 0000000000000100 sp > 00007fff9805d758 error 14 in icon-theme.cache[7f0a5f99d000+41bb000] > [10199.843439] chromium[6900]: segfault at 64 ip 0000000000000064 sp > 00007fff2d271298 error 14 in libspeexdsp.so.1.5.0[7fa88a878000+12000] [...] > The update came in this morning, then the floodgate opened. [...] > I've attached the dpkg.log for yesterday's upgrade for your reference. [...] > I installed libexif12-0.6.20-2 from the site you gave me and chromium > seems to be quite stable. > > I tried it on both my home and work machine and chromium didn't crash > on me at all. Thanks, Hans. libexif maintainers: to summarize, after upgrading libexif12 from 0.6.20-2 to 0.6.20-3, Hans started experiencing symptoms of data corruption in chromium. Downgrading libexif fixed it again. Known problem? Any ideas for tracking it down? Hope that helps, Jonathan [1] http://bugs.debian.org/682616 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
