Arch Linux User Repository

@malah: The package is not out of date, the latest released version is 6.3.1 so you did wrong flagging the package as out-of-date. Regarding the theme use, see comment on 2015-04-23: the application hangs when you complete a form project if you do not use a GTK 2.0 theme (upstream issue).

@Frontier Why did you use a custom theme ?

When I try to run the program from my xfce4 menu, I get the error: Failed to execute child process "GTK2_RC_FILES=/usr/share/themes/Raleigh/gtk-2.0/gtkrc" (No such file or directory) I was able to overcome this problem by editing /usr/share/applications/jaspersoftstudio.desktop and changing: Exec=GTK2_RC_FILES=/usr/share/themes/Raleigh/gtk-2.0/gtkrc /opt/jaspersoftstudio/Jaspersoft Studio to: [bad change deleted] Edit: the correct change is: Exec=env GTK2_RC_FILES=/usr/share/themes/Raleigh/gtk-2.0/gtkrc "/opt/jaspersoftstudio/Jaspersoft Studio"

@drencrom: Thank you very much for the suggestion, PKGBUILD updated.

There is a bug in the PKGBUILD file. The variable _binname="Jaspersoft\\ Studio" should not have the \\ as it already has parenthesis. The symbolic link from /usr/bin does not work because it points to "/opt/jaspersoftstudio/Jaspersoft\ Studio" instead of pointing to "/opt/jaspersoftstudio/Jaspersoft Studio"

@shilka: Thank you very much for your contribution, I have updated the package.

The .desktop file generated in PKGBUILD has a small bug. The real pkgdir in /opt is all lower case alphabets, but in .desktop file it seems different. Further, because of the executable file name contain a space, the file name used in Exec line should be amended by add two backslash as escape char. Regards,

Updated PKGBUILD using Raleigh GTK2 theme workaround.

@Hf2094: After some tests I've discovered a workaround: Jaspersoft Studio 6.0.4 works fine when using any other GTK2+ theme than OxygenGTK (e.g I am using it with Raleigh without crashes). It does not blend nice with my KDE workspace however...

@Hf2094: On my system (ASUS Z87-Pro, Intel i7 4770K) using OpenJDK 8 (after editing /opt/jaspersoftstudio/Jaspersoft Studio.ini and removing the -vm specification) and following the steps you describe, Jaspersoft Studio crashes with the following error: A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007fe85af753dd, pid=6896, tid=140637146633984 # # JRE version: OpenJDK Runtime Environment (8.0_40-b25) (build 1.8.0_40-b25) # Java VM: OpenJDK 64-Bit Server VM (25.40-b25 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libgobject-2.0.so.0+0x333dd] g_type_check_instance_is_fundamentally_a+0xd # # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again # # An error report file with more information is saved as: # /tmp/hs_err_pid6896.log Compiled method (nm) 134288 3799 n 0 org.eclipse.swt.internal.gtk.OS::_g_object_get_qdata (native) total in heap [0x00007fe88dd3e090,0x00007fe88dd3e3f0] = 864 relocation [0x00007fe88dd3e1b8,0x00007fe88dd3e200] = 72 main code [0x00007fe88dd3e200,0x00007fe88dd3e3e8] = 488 oops [0x00007fe88dd3e3e8,0x00007fe88dd3e3f0] = 8 # # If you would like to submit a bug report, please visit: # http://bugreport.java.com/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. The crash is related to a well-known and - quite old - bug in Eclipse: https://bugs.eclipse.org/bugs/show_bug.cgi?id=419729 This error is GTK specific and some have used this workaround https://bugs.eclipse.org/bugs/show_bug.cgi?id=430736#c48 or this workaround https://bugs.eclipse.org/bugs/show_bug.cgi?id=430736#c50 The other solution is to downgrade to 6.0.3 which used to work fine on my machine as none of the above workarounds fixed the problem.