Ticket #1160 (new Support Requests)

Opened 3 months ago

Last modified 3 months ago

Upgrade 1.4.6 to 1.6.2 on Suse Linux 10.3 does not work

Reported by: schmitt@med.uni-rostock.de Assigned to:
Priority: 5, normal Milestone: To Be Decided by Jajuk Team
Component: (Jajuk Members) Any (Default Component) Version: 1.6.2
Keywords: Updrade Problem Linux Cc:

Description

I want to upgrade Jajuk 1.4.6 to 1.6.2 on Linux Suse 10.3 by using rpm -Uvh jajuk-${version}-noarch.rpm

on /home/xuser/JukeboxPowerPack/jajuk-1.6.2.noarch.rpm

where my jajuk 1.4.6 files are installed.

After executing rpm -Uvh jajuk-${version}-noarch.rpm as root starting jajuk again as user groop member only makes use of the old 1.4.6 version. If I try to install rpm -Uvh jajuk-${version}-noarch.rpm again rpm tells me that everything is already installed.

Has anybody an idea why 1.6.2 do not start after upgrading 1.4.6 ?

THANKS, Ol

Attachments

Change History

07/11/08 18:54:50 changed by anonymous

Your user probably doesn't use the right binary. Jajuk is normally installed in /usr/bin (in both 1.4.2 and 1.6 AFAIK). If you launch jajuk from command line, check the output of $ type jajuk

otherwise, check the link you use

Make sure also that your RPM -U command really ran propertly.

07/11/08 18:55:17 changed by bflorat

  • type changed from Discussion to Support Requests.

07/11/08 19:49:12 changed by schmitt@med.uni-rostock.de

The Version 1.4.6 with jar's was somewhere hidden in /home/xxx and the Upgrade jar's are hidden in /usr/share. I've fixed the problem by a short sh script:

export LIBXCB_ALLOW_SLOPPY_LOCK=true /usr/java/jre1.6.0_03/bin/java -Djava.library.path=/usr/share/jajuk/lib -client -Xms20M -Xmx512M -jar /usr/share/jajuk/bin/jajuk.jar -notest

Thanks for help, Ol

07/13/08 23:10:01 changed by bflorat

OK. However, I still can't understand how your problem can happen as the /usr/bin/jajuk script makes a 'cd' to the right directory containning the right jar:

##Go in the right /bin directory #test if jajuk has been installed in default directory /usr/lib/jajuk/ via RPM/Deb package if [ "/usr/bin/jajuk" = "$0" ] && [ -e /usr/share/jajuk/bin/jajuk.jar ] ; then

JAJUK_HOME="/usr/share/jajuk/bin" cd /usr/share/jajuk/bin

else

JAJUK_HOME="dirname $0/bin" cd dirname $0/bin

fi ... $JAVA_BIN $JAVA_OPTIONS -jar jajuk.jar $JAJUK_OPTIONS

Was your PATH set so you actually used /usr/bin/jajuk script to launch jajuk ?

PS: why do you set LIBXCB_ALLOW_SLOPPY_LOCK ?

07/14/08 09:23:19 changed by anonymous

Well,

export LIBXCB_ALLOW_SLOPPY_LOCK=true

is necessary because the libcxb for Linux have a problem with each Java (4, 5, 6) producing the following error message:

java: xcb_xlib.c:82: xcb_xlib_unlock: Assertion `c->xlib.lock' failed.

Using export LIBXCB_ALLOW_SLOPPY_LOCK=true solves this problem for all Java application on Linus OS.

The problem with the paths is curious, since the upgraded jar was installed into /usr/share/jajuk/bin/jajuk.jar. I thing that within installation of the upgrade 1.6.2 - which I've done as root - the paths or the path variable were not updated. Maybe an improvement could be to create a new link in the "program list" of kde or on the desktop by applying the jajuk upgrade.

07/14/08 21:55:36 changed by anonymous

Actually, we provide a generic RPM and we no more support Suse specific RPM among others reasons because the menu system seems buggy (at least until Suse 10.2) and we never manage to update or even create menu entries.

Add/Change #1160 (Upgrade 1.4.6 to 1.6.2 on Suse Linux 10.3 does not work)