FS#9428 - Patch to frostwire startup script, solves bug with custom java options.

Attached to Project: Arch Linux
Opened by Ramses de Norre (Ramses_de_Norre) - Friday, 01 February 2008, 13:57 GMT
Last edited by Tom Killian (tomk) - Thursday, 17 April 2008, 21:42 GMT
Task Type Feature Request
Category Packages: Unstable
Status Closed
Assigned To Tom Killian (tomk)
Architecture All
Severity Low
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

Frostwire's runFrostwire.sh script checks the available java version by evaluating the first line of "java -version", if you add custom options to java, however, these options are outputted before the line frostwire expects as the first one. I've changed one line in the script and the problem seems solved now. I'm adding the patch, hopefully the problem gets fixed this way.

I'll post this to the frostwire bug tracker too.

Additional info:
* package version(s)
4.13.3-1
* config and/or log files etc.


Steps to reproduce: try to run frostwire with custom java options set in .bashrc, e.g. " export _JAVA_OPTIONS="-Dswing.defaultlaf=com.sun.java.swing.plaf.gtk.GTKLookAndFeel" "
This task depends upon

Closed by  Tom Killian (tomk)
Thursday, 17 April 2008, 21:42 GMT
Reason for closing:  Implemented
Additional comments about closing:  Patch applied to 4.13.5-1, now in the extra repo. Upstream application would be preferable, so this will be reviewed for future releases.
Comment by Ramses de Norre (Ramses_de_Norre) - Friday, 01 February 2008, 13:58 GMT
It seems the patch didn't came through, hoepfully it is included now.
   runfrostwire_sh.patch (0.5 KiB)

Loading...