Date: Tue, 28 Jul 2009 21:06:21 +0300 From: Andriy Gapon <avg@icyb.net.ua> To: Joe Marcus Clarke <marcus@freebsd.org> Cc: ports@freebsd.org, gnome@freebsd.org Subject: Re: after update - not all jpeg files are displayable Message-ID: <4A6F3E1D.6060404@icyb.net.ua> In-Reply-To: <4A6F36F6.5060805@freebsd.org> References: <20090728164118.4f36a21f.lehmann__19447.6383309395$1248793624$gmane$org@ans-netz.de> <4A6F282A.2060400@icyb.net.ua> <4A6F2DD8.9090909@freebsd.org> <4A6F2FCA.2080908@icyb.net.ua> <4A6F36F6.5060805@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
on 28/07/2009 20:35 Joe Marcus Clarke said the following: > Andriy Gapon wrote: >> on 28/07/2009 19:56 Joe Marcus Clarke said the following: >>> No. It's an issue with an incomplete PORTREVISION bump on ports which >>> depend on libjpeg. Really, you need to do a portupgrade -rf jpeg to fix >>> this. What you must avoid is one port being linked to both jpeg.9 and >>> .10. When that happens, applications crash trying to open JPEGs. >> This is not an issue for me as far I can see. >> libchk reported that no binaries/libraries were linked to libjpeg.so.9 in >> lib/compat/pkg - I have even removed it now from . >> Everything is linked to libjpeg.so.10, no unresolved libraries. >> >> Any further suggestions? >> Maybe you could try to reproduce the issue for yourself? > > I did with eog. As soon as a forced a rebuild, all JPEGs opened just > fine again. The sample Final_Frontier.jpg works fine for me in eog, and > with Nautilus thumbnail generation. I tried eog too, works flawlessly here. Still gqview has the problem as the original reported said. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A6F3E1D.6060404>