Warning: file_exists(): open_basedir restriction in effect. File(/srv/http/vhosts/aur.archlinux.org/public/web/locale//en/LC_MESSAGES/aurweb.mo) is not within the allowed path(s): (/srv/http/vhosts/aur-dev.archlinux.org/:/etc/aurweb/) in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/streams.php on line 90
AUR (en) - jaspersoftstudio

Notice: Undefined variable: name in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/pkgfuncs.inc.php on line 248

Package Details: jaspersoftstudio 6.3.1-1

Git Clone URL: https://aur-dev.archlinux.org/jaspersoftstudio.git (read-only)
Package Base: jaspersoftstudio
Description: Eclipse based Jasper Reports generator
Upstream URL: http://community.jaspersoft.com/project/jaspersoft-studio
Licenses: Eclipse
Submitter: Circuitsoft
Maintainer: Frontier
Last Packager: Frontier
Votes: 9
Popularity: 0.146255
First Submitted: 2014-01-11 01:44
Last Updated: 2016-10-04 15:00

Latest Comments

1 2 Next › Last »

asgillett commented on 2016-03-31 22:26

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"

Frontier commented on 2016-03-23 14:41

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

drencrom commented on 2016-03-23 12:27

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"

Frontier commented on 2015-10-02 10:40

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

shilka commented on 2015-09-25 15:40

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,

Frontier commented on 2015-04-27 06:59

Updated PKGBUILD using Raleigh GTK2 theme workaround.

Frontier commented on 2015-04-24 16:44

@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...

Frontier commented on 2015-04-23 17:51

@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 commented on 2015-04-23 17:43

@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 commented on 2015-04-23 17:11

@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.

Unfortunately I cannot suggest anything else right now other than downgrading to 6.0.3 and see if it works. I've done some reports on 6.0.3 without issues and these crash on 6.0.4.