Arch Linux

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.

@Frontier: How did you get this product going under ArchLinux? When I load an existing iReport-JRXML into Jaspersoftstudio or when I create a new report with Jaspersoftstudio the Outline View is empty and Jaspersoftstudio does not repond to mouseclicks.

In ~/JaspersoftWorkspace/.metadata/.log I see a lot of

"java.lang.RuntimeException: Widget disposed too early ..." (e.g ...for part org.eclipse.ui.views.ProblemView; and others).

My system:
Mainboard: MSI A88X-G43 (MS-7793)
CPU: AMD Athlon(tm) X4 860K Quad Core Processor
Memory: 4GB
OS: Linux xxx 3.19.3-3-ARCH #1 SMP PREEMPT Wed Apr 8 14:10:00 CEST 2015 x86_64 GNU/Linux
Repositories: core, community and extras; no testing repos, no multilib repo
Java:
extra/java-commons-daemon 1.0.15-2
community/java-commons-logging 1.2-1
extra/java-jline 1.0-3
extra/java-jsvc 1.0.15-2
extra/java-rhino 1.7R4-2
extra/java-runtime-common 2-2
extra/jre7-openjdk 7.u79_2.5.5-1
extra/jre7-openjdk-headless 7.u79_2.5.5-1

I tried the same installation of Jaspersoftstudio on my system by mounting the containing partition under different other OSes:

- Debian Wheezy (worked)
- Centos7 (failed)
- Fedora21 (worked)

Regards
Rudolf H.

@Cris70: Are you using OpenJDK 7 or 8? As I recall, Manjaro has v7 enabled by default. I am using Jaspersoft Studio with OpenJDK8u31 on Arch Linux x64 connecting to JDBC databases without problems leading to the exception error message you mention.

There is another possibility however: the original TIBCO Jaspersoft Studio package lacks the necessary connector library for the server you are trying to connect, hence the exception.

The PKGBUILD does not remove anything - regarding functionality - from the original Linux package. Can you try using (as a user) the original TIBCO Jaspersoft Studio 6.0.3 package on your system and see if the problem persists?

v6.0.3 is not working correctly here (Manjaro Linux 0.8.12).
Every time I try to configure a connection to a remote JasperReports server I get this error when testing the connection:

java.lang.IllegalArgumentException: Username may not be null

Obviously I filled the username and password fields.

Here's an update for 5.6.1:

http://pastebin.com/tpaG3h6h

http://community.jaspersoft.com/wiki/crash-when-running-gnome-3