The package is present in Portage as dev-libs/iniparser, would be a nice idea to get upstream to use the system copy if present so we don't have to add yet another copy of it.
Fixed on libcompizconfig-0.8.2-r1. ppc/ppc64 I had to drop your keywords until you keyword dev-libs/iniparser. Please keyword at your convenience.
Not fixed at all; seems like libcompizconfig uses internal code of the iniparser library, you didn't check that compiz started up after your patch, did you?
ccsm Info: No sexy-python package found, don't worry it's optional. Traceback (most recent call last): File "/usr/bin/ccsm", line 99, in <module> import compizconfig ImportError: /usr/lib/libcompizconfig.so.0: undefined symbol: iniparser_setstr Have a similar problem * dev-libs/iniparser Available versions: (~)3.0b
Can't start compiz-manager after apply the patch, /usr/lib/libcompizconfig.so.0: undefined symbol: iniparser_new
I've same problem
Yep r1 is broken. emerge -v =x11-libs/libcompizconfig-0.8.2 Fixes the problem mentioned
(In reply to comment #2) > Not fixed at all; seems like libcompizconfig uses internal code of the > iniparser library, you didn't check that compiz started up after your patch, > did you? I see I broke libcompizconfig. I'll try to see what I can do to it when I get home.
(In reply to comment #6) > Yep r1 is broken. I've asked Tomas Chvatal (scarabeus) to mask libcompizconfig-0.8.2-r1.
*** Bug 267666 has been marked as a duplicate of this bug. ***
Created attachment 189689 [details, diff] Updated patch to allow libcompizconfig to build against the system iniparser This patch changes the function names to allow libcompizconfig to build against the system iniparser. Currently there will still be one implicitly defined function (iniparser_set) as the iniparser.h installed by dev-libs/iniparser is inconsistent with the functions defined by iniparser.c in the same package. I'll file a bug for that and make it block this one.
John, could you please submit a cleaned up patch, skipping autotools regeneration and just providing the actual changes you edited yourself? You should be able to either use a git checkout of the libcompizconfig repository or quilt to get the clean patch.
Created attachment 190123 [details, diff] Updated patch with only the minimal necessary changes I've updated the patch to include only the necessary changes (the autoconf changes from the patch currently in portage and my changes to the source to allow it to build). I'm still not 100% happy with this since I've had to knock out iniparser.h completely from the source to ensure that it isn't included, which means that the configure changes to use the system iniparser are more or less redundant since applying this patch will force you to use iniparser.h from your system.
.. could someone please mask 0.8.2-r1? 0.8.2 works. 0.8.2-r1 does not.
(In reply to comment #13) > .. could someone please mask 0.8.2-r1? 0.8.2 works. 0.8.2-r1 does not. > here on amd64 0.8.2-r2 works great
sorry.. had it unmasked locally.
I bumped libcompizconfig to 0.8.2-r2 in the overlay with the latest patch - thanks to John Keeping. Will update the ebuild in the tree shortly.
I just added the updated ebuild to the tree. @ppc, @ppc64: I had to drop your keywords for x11-libs/libcompizconfig-0.8.2-r2 as you're still missing keywords for dev-libs/iniparser-3.0b-r1
I just upgraded to 0.8.2-r2 from the overlay and it's the same, compiz won't start. If i execute compiz --replace i get: compiz (core) - Error: Couldn't load plugin 'yes' When executing fusion-icon i get no message, it simply doesn't start, but when i change to kwin i get the error and backtrace of the attachment.
Created attachment 198256 [details] Error message from fusion-icon
(In reply to comment #19) > Created an attachment (id=198256) [edit] > Error message from fusion-icon > also here on x86 compiz doesn't start anymore after the upgrade, I get the following error : compiz --replace compiz (core) - Fatal: GLX_EXT_texture_from_pixmap is missing compiz (core) - Error: Failed to manage screen: 0 compiz (core) - Fatal: No manageable screens found on display :0.0
My problem could be related to xorg ati drivers because on my amd64 machine I have nvidia propertary drivers and on that machine compiz still works also after the upgrade and on other two x86 machines I have ati xorg driver and compiz stopped working with the error I reported above. Downgrading libcompizconfig on x86 machines to 0.8.2 makes compiz work again. Should I open another bug for this ?
(In reply to comment #21) > Should I open another bug for this ? Please do.
(In reply to comment #22) > (In reply to comment #21) > > Should I open another bug for this ? > > Please do. > opened bug #278132
I have the same error as Chema on 0.8.2-r2 on amd64 / nvidia proprietary drivers. compiz seems to start, but all settings are wiped and any attempt to change them results in them resetting again. At one point, I believe I looked at the Default.ini and the format was very different from what it is on 0.8.2, but I've downgraded to fix the problem and don't have a copy of the -r2 ini.
I forgot to add a comment here that libcompizconfig-0.8.2-r2 has been masked. I'll keep working on this.
ppc/ppc64 have iniparser marked, please add us back when we're needed.
Bug too under 0.8.4: compiz (core) - Error: Couldn't load plugin 'yes'
Created attachment 321770 [details, diff] Patch for libcompizconfig-0.8.8.ebuild Bug still presents in libcompizconfig-0.8.8.ebuild Suggesting patch for ebuild to fix in. Please commit it as 0.8.8-r1
The patch mostly seems fine. However I'm not completely sure libcompizconfig-0.8.2/src/ini.c change. Are there any upstream discussion about this issue?
(In reply to comment #29) > The patch mostly seems fine. However I'm not completely sure > libcompizconfig-0.8.2/src/ini.c change. Are there any upstream discussion > about this issue? No, i did not find any discussion about that. It seems that upstream thinks that this is normal behaviour
Comment on attachment 321770 [details, diff] Patch for libcompizconfig-0.8.8.ebuild It seems that this patch is someway broken - with it ini files are broken and unusuable :-(
removed from the tree
