I don't think libexif is the problem since this crashed occured with
version 0.6.20-2 of the package...
BTW I disabled all plugins and I cannot reproduce it anymore, must have
been a plugin then.
Eugenio
On Sat, Jul 28, 2012 at 5:21 PM, Onur Aslan o...@onur.im wrote:
We know this bug occurred
Hi,
Eugenio Cano-Manuel Mendoza wrote:
I don't think libexif is the problem since this crashed occured with
version 0.6.20-2 of the package...
That's new information. So do I understand correctly that:
- when you first experienced the bug, you had libexif 0.6.20-2 installed
and it was
Hi,
Sorry I wasn't clear enough.
-The first time I experienced the bug I had libexif 0.6.20-3 installed
and it was reproducible.
-After you asked me to downgrade I installed libexif 0.6.20-2, the bug
was still reproducible.
-I was later asked to try to get a trace from gdb, I have never
been
We know this bug occurred when we upgrade libexif to 0.6.20-3. One of that
security patch broke the package.
Instead of downgrading libexif to 0.6.20-2, I made a package for 0.6.21. It
includes security fixes and chromium crashes are gone.
You can get it here and use it until libexif maintainers
Hi,
On Thu, Jul 26, 2012 at 09:52:26AM -0500, Jonathan Nieder wrote:
reassign 682616 libexif12 0.6.20-3
affects 682616 + chromium src:chromium-browser
quit
Eugenio Cano-Manuel Mendoza wrote:
On Thu, Jul 26, 2012 at 10:16 PM, Jonathan Nieder jrnie...@gmail.comwrote:
Eugenio Cano-Manuel
