Date: Wed, 29 Jul 2009 11:26:21 +1000 From: Andrew Reilly <andrew-freebsd@areilly.bpc-users.org> To: Oliver Lehmann <lehmann@ans-netz.de> Cc: ports@freebsd.org, gnome@freebsd.org, Joe Marcus Clarke <marcus@freebsd.org>, Andriy Gapon <avg@icyb.net.ua> Subject: Re: after update - not all jpeg files are displayable Message-ID: <20090729012621.GA96134@duncan.reilly.home> In-Reply-To: <20090728194108.7297e9fe.lehmann@ans-netz.de> References: <20090728164118.4f36a21f.lehmann__19447.6383309395$1248793624$gmane$org@ans-netz.de> <4A6F282A.2060400@icyb.net.ua> <4A6F2DD8.9090909@freebsd.org> <20090728194108.7297e9fe.lehmann@ans-netz.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jul 28, 2009 at 07:41:08PM +0200, Oliver Lehmann wrote: > Joe Marcus Clarke wrote: > > > 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. > > Hm - I cannot see which library could be causing this - I still have some > jpeg.9 using stuff but this seems not the cause here? There's something else going wrong, IMO. I did the -r jpeg upgrade, and have done an ldd trawl through /usr/local/bin and /usr/local/lib, and come up blank, and yet geequie frequently shows a black screen when I point it to a jpg. This isn't specific to particular jpg files: if I select another, it'll probably display OK, and then click back to the "bad" one and it may display OK too. Haven't got to the bottom of it yet. It's possible that only geequie and gqview (parent of geequie, I think) are at fault, somehow. Cheers, -- Andrew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090729012621.GA96134>