Hi,
chromium-browser did not start with the -f option for some reason...
however I managed to reproduce the segfault and this is the trace:
strace -e open chromium-browser 2>&1 | grep icon-theme.cache | grep -v
ENOENT
open("/usr/share/icons/gnome/icon-theme.cache", O_RDONLY|O_LARGEFILE) = 68
open("/usr/share/icons/gnome/icon-theme.cache", O_RDONLY|O_LARGEFILE) = 69
open("/usr/share/icons/hicolor/icon-theme.cache", O_RDONLY|O_LARGEFILE) = 68
open("/usr/share/icons/hicolor/icon-theme.cache", O_RDONLY|O_LARGEFILE) = 69
zsh: segmentation fault strace -e open chromium-browser 2>&1 |
zsh: done grep icon-theme.cache | grep -v ENOENT
I have to mention that I ran this using libexif 0.6.20-3, I'll try with
0.6.20-2 soon.
Cheers,
Eugenio
On Fri, Jul 27, 2012 at 3:43 AM, Jonathan Nieder <jrnie...@gmail.com> wrote:
> Hi,
>
> Emmanuel Bouthenot wrote:
>
> > I'll be glad if the people able to reproduce this bug could attach to
> > this bug report the result of the following command:
> >
> > # strace -e open chromium-browser 2>&1|grep icon-theme.cache|grep -v
> ENOENT
>
> /usr/bin/chromium-browser is a shell script, so presumably you'll
> rather want output from
>
> strace -f -e open chromium-browser --single-process 2>&1 |
> grep icon-theme.cache |
> grep -v ENOENT
>
> Hans, Eugenio, is this reproducible with --single-process?
>
> Thanks,
> Jonathan
>
