[arch-general] kernel26-2.6.32.6-1 updates breaks Compiz?

Ng Oon-Ee ngoonee at gmail.com
Sat Jan 30 07:50:12 EST 2010


On Sat, 2010-01-30 at 13:51 +0200, Ionut Biru wrote:
> On 01/30/2010 01:03 PM, Ng Oon-Ee wrote:
> > On Sat, 2010-01-30 at 05:03 -0500, Eric Bélanger wrote:
> >> 2010/1/30 Ng Oon-Ee<ngoonee at gmail.com>:
> >>> On Fri, 2010-01-29 at 13:19 +0200, Ionut Biru wrote:
> >>>> On 01/29/2010 10:33 AM, Ng Oon-Ee wrote:
> >>>>> On Fri, Jan 29, 2010 at 11:23 AM, Ng Oon-Ee<ngoonee at gmail.com>   wrote:
> >>>>>
> >>>>> Update, I've found that disabling the 'png' plugin under the 'Image
> >>>>> Loading' section "fixes" the issue, at least compiz loads up and runs
> >>>>> like it used to. Something must have gone wrong with the
> >>>>> libpng-related rebuild. Bug report time?
> >>>>
> >>>> do
> >>>>
> >>>> LD_DEBUG=files fusion-icon>  log 2>&1
> >>>>
> >>>> post somewhere the log and then post here the link to see it
> >>>>
> >>>
> >>> Here's the log from a failed run - http://pastebin.com/m6a6cb270
> >>>
> >>> Here's the log from a successful run (with the png plugin turned off) -
> >>> http://pastebin.com/m62782b96
> >>>
> >>> Both pastebins only available for a month. Interesting line (in my
> >>> unexperienced opinion) in the first log is line 1914:-
> >>>       7720:     /usr/lib/compiz/libpng.so: error: symbol lookup error:
> >>> undefined symbol: png_check_sig (fatal)
> >>> compiz: symbol lookup error: /usr/lib/compiz/libpng.so: undefined
> >>> symbol: png_check_sig
> >>>
> >>
> >> It needs to be patched for the new libpng. Open a bug report if there isn't one.
> >
> > I understand this version IS patched for the new libpng, since it was
> > held in testing just like all the other libpng packages.
> >
> > http://bugs.archlinux.org/task/18076 is the bug report I just posted.
> >
> 
> i was surprised to see that there is an similar bug report.
> i've just uploaded 0.8.4-3, please test it
> 

Hi wonder, I was surprised to see you dup my bug as well, since I did do
a search and didn't find the previous.

In any case, 0.8.4-3 solves my issue. Thanks. Posting the same on the
bug-tracker now.



More information about the arch-general mailing list