FS#16162 - [strigi] does not find OpenJDK 1.6.0

Attached to Project: Arch Linux
Opened by mutlu inek (mutlu_inek) - Saturday, 12 September 2009, 22:15 GMT
Last edited by Andrea Scarpino (BaSh) - Saturday, 03 October 2009, 18:02 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Andreas Radke (AndyRTR)
Andrea Scarpino (BaSh)
Architecture All
Severity Low
Priority Normal
Reported Version 3.3.0
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Summary and Info:
Strigi does not start since the upgrade of OpenJDK to version 1.6.0.

An entry in the Chakra forums suggests doing the following, which remedies the problem:
1) console: sudo nano /etc/ld.so.conf
2) Add for your architecture..
64 bit: /opt/java/jre/lib/amd64/server
32 bit: /opt/java/jre/lib/i386/server
3) console: sudo ldconfig
(See http://chakra-project.org/bbs/viewtopic.php?pid=5845)

Steps to Reproduce:
Open KDE's systemsettings, go to the advanced tab, choose "Desktop Search", select the (since the upgrade disabled) option "Enable Strigi Desktop file indexer" and click "Apply." Strigi will complain about an "installation problem," the typical error message when there is no Java RE or no Sesame2 backend available.
This task depends upon

Closed by  Andrea Scarpino (BaSh)
Saturday, 03 October 2009, 18:02 GMT
Reason for closing:  Fixed
Additional comments about closing:  soprano 2.3.1-1
Comment by mutlu inek (mutlu_inek) - Saturday, 12 September 2009, 22:16 GMT
Sorry for attaching this report to pacman. Please reassign. Thank you.
Comment by Pierre Schmitz (Pierre) - Sunday, 13 September 2009, 11:55 GMT
Works fine here with openjdk6 and jre. The mentioned adjustments to ld.so.conf are not necessary. Did you try to remove the strigi/nepomuk files /dirs from .kde4? Or does it work with a newly created user?
Comment by mutlu inek (mutlu_inek) - Sunday, 13 September 2009, 18:29 GMT
I created a new user, which then ran into the same problem.
Comment by Pierre Schmitz (Pierre) - Sunday, 13 September 2009, 18:35 GMT
Are you using kdemod?
Comment by mutlu inek (mutlu_inek) - Sunday, 13 September 2009, 18:55 GMT
I removed OpenJDK and installed Sun's JRE. Doing "ldd /usr/lib/soprano/libsoprano_sesame2backend.so" returns "libjvm.so => not found".

Editing /etc/ld.so.conf as described above and running ldconfig solves the problem: running "ldd /usr/lib/soprano/libsoprano_sesame2backend.so" now returns "libjvm.so => /opt/java/jre/lib/i386/server/libjvm.so (0xb7308000)".

Activating strigi in systemsettings after following these steps makes strigi start.

Comment by mutlu inek (mutlu_inek) - Sunday, 13 September 2009, 18:55 GMT
No, I am not using KDEMod/Chakra.
Comment by Marcello Maggioni (Kariddi) - Monday, 14 September 2009, 15:40 GMT
I have this problem and I'm NOT using KDEMod
Comment by Andreas Radke (AndyRTR) - Monday, 21 September 2009, 20:17 GMT
I'm afraid the i686 soprano(?) pkg has been built against Sun's jre/jdk and not in a clean chroot...
Comment by Pierre Schmitz (Pierre) - Monday, 21 September 2009, 20:23 GMT
I doubt it as the PKGBUILD has openjdk6 as makedepends.
Comment by mutlu inek (mutlu_inek) - Tuesday, 22 September 2009, 19:50 GMT
I might not understand properly what you are trying to get at, Andreas, but shouldn't the package work with Sun's JRE, if it was actually built against it? For me, it does not.

Just to repeat: It does not work at all with OpenJDK. And it does not work with Sun's JRE out of the box, either. To be able to use Sun's JRE, ld.so.conf has to be modified.
Comment by Andrea Scarpino (BaSh) - Friday, 02 October 2009, 16:07 GMT
the soprano package was build not in a clean chroot but with openjdk6. I don't use sun's jre/jdk.
Anyway I updated soprano to 2.3.1 (built in a clean chroot) who should fix  FS#16194  and this one too.

Loading...