| Summary: | Systemsettings of kolor-manager module crashes systemsettings | ||
|---|---|---|---|
| Product: | [Applications] systemsettings | Reporter: | Benjamin Schindler <beschindler> |
| Component: | kcm_oyranos | Assignee: | Kai-Uwe Behrmann <ku.b> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | asturm, enrico.tagliavini, kde, ku.b, magnus.kessler, timo.gurr |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
|
Description
Benjamin Schindler
2013-02-10 13:42:18 UTC
> /usr/lib64/elektra/libelektra-resolver.so: undefined symbol: elektraPluginExport
Such message is typical example of (downstream) binary compatibility problem. You could try rebuilding elektra or related packages.
T.b.h. I have a hard time believing this, because of 2 reasons: - I just installed kolor-manager, which in turn pulled in elektra as well. So both builds are as fresh as they can be - I don't know the workings of elektra/kolor-manager, but it seems to me, that we have a sequence of dlopen, dlsym sequence, where dlsym fails to find the appropriate symbol (if it were an unresolved symbol, kolor-manager would not have built). So the question is, why does dlsym fail. This is why I thought its an elektra issue @Benjamin which version of Elektra and Oyranos do you build? Have you some elder builds or binaries laying around? app-admin/elektra-0.8.3 media-libs/oyranos-0.9.1 I didn't have neither elektra nor oyranos installed before on this system, so I doubt that there are older builds around (In reply to comment #4) > app-admin/elektra-0.8.3 > media-libs/oyranos-0.9.1 They do not work together. elektra-0.8 introduced API changes, which Oyranos is not up to. As a workaround use an elektra-0.7.x. A version of 0.7.x is included in the Oyranos tarball and should work in newer packages. Aha, thanks - this is an important hint. May be change this bug report to a feature request for oryanos that it should detect that. The gentoo devs were not aware of it. I'll report a bug for gentoo, but the oryanos build system should detect that! The systemsettings crash is actually solved by starting it with: LD_PRELOAD=/usr/lib64/libelektra.so elektra-0.7.1 still exists in portage tree but that version doesn't get upstream love anymore and needs several downstream modifications to avoid colliding with other packages for silly file naming reasons, so having oyranos compatible with latest elektra versions would be preferable. (In reply to comment #7) > The systemsettings crash is actually solved by starting it with: > LD_PRELOAD=/usr/lib64/libelektra.so > > elektra-0.7.1 still exists in portage tree but that version doesn't get > upstream love anymore and needs several downstream modifications to avoid > colliding with other packages for silly file naming reasons, so having > oyranos compatible with latest elektra versions would be preferable. While I agree that the best solution is having oyranos be compatible with elektra-0.8, that's up to the oyranos devs. Just putting in LD_PRELOAD to make things load is extremely dangerous - at least I have no idea whether there are more breakages and whether they will be so obvious. So please, let the oyranos people handle this. And apart from that - that's a discussion for bugs.gentoo.org :) Supporting elektra-0.8.x is a good aim. A feature request is upstream to prioritise in Oyranos: https://sourceforge.net/tracker/?func=detail&aid=3604063&group_id=177017&atid=879556 Fix confirmed using today's build of oyranos master and elektra-0.8.4 (0.8.3 did segfault). @andreas thanks for the confirmation |