New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Severe UI malfunction under Mac OS X 10.7.5 #171

Open
DavidMenting opened this Issue Jul 26, 2013 · 9 comments

Comments

Projects
None yet
5 participants
@DavidMenting

DavidMenting commented Jul 26, 2013

Since installing a Java update on OS X 10.7.5 (now Java version 1.6.0_51) Visicut has a severely malfunctioning user interface. It starts empty and only redraws when you resize the window:

screen shot 2013-07-26 at 16 24 04

Log entries look like this:

26-07-13 16:27:51,072 JavaApplicationStub: CGContextGetCTM: invalid context 0x0
26-07-13 16:27:51,072 JavaApplicationStub: CGContextSetBaseCTM: invalid context 0x0
26-07-13 16:27:51,072 [0x0-0x38f38f].com.t_oster.visicut.gui.VisicutApp: Jul 26 16:27:51 Davids-MacBook-Air.local JavaApplicationStub[6761] : CGContextGetCTM: invalid context 0x0
26-07-13 16:27:51,073 [0x0-0x38f38f].com.t_oster.visicut.gui.VisicutApp: Jul 26 16:27:51 Davids-MacBook-Air.local JavaApplicationStub[6761] : CGContextSetBaseCTM: invalid context 0x0
26-07-13 16:27:51,073 JavaApplicationStub: CGContextGetCTM: invalid context 0x0
26-07-13 16:27:51,073 JavaApplicationStub: CGContextSetBaseCTM: invalid context 0x0
26-07-13 16:27:51,073 [0x0-0x38f38f].com.t_oster.visicut.gui.VisicutApp: Jul 26 16:27:51 Davids-MacBook-Air.local JavaApplicationStub[6761] : CGContextGetCTM: invalid context 0x0
26-07-13 16:27:51,073 [0x0-0x38f38f].com.t_oster.visicut.gui.VisicutApp: Jul 26 16:27:51 Davids-MacBook-Air.local JavaApplicationStub[6761] : CGContextSetBaseCTM: invalid context 0x0

The program is unusable. Dialog boxes don't pop up and it is impossible to click buttons.

I might try a downgrade of the installed Java version to see if Visicut starts working normally again.

@t-oster

This comment has been minimized.

Show comment
Hide comment
@t-oster

t-oster Jul 26, 2013

Owner

Hi,please try downloading the platform independent zip version and see if the error also exists there. The OSX package contains a (maybe outdated) java application stub, while the os independent version starts java directly.

Owner

t-oster commented Jul 26, 2013

Hi,please try downloading the platform independent zip version and see if the error also exists there. The OSX package contains a (maybe outdated) java application stub, while the os independent version starts java directly.

@DavidMenting

This comment has been minimized.

Show comment
Hide comment
@DavidMenting

DavidMenting Jul 26, 2013

Downgrading tot Java version 1.6.0_45 made VisiCut work again.

I did as you suggested: reinstalled Java 1.6.0_51 and downloaded the OS independent version. It works perfectly so it would be nice if the Mac OSX package gets fixed. Thanks!

DavidMenting commented Jul 26, 2013

Downgrading tot Java version 1.6.0_45 made VisiCut work again.

I did as you suggested: reinstalled Java 1.6.0_51 and downloaded the OS independent version. It works perfectly so it would be nice if the Mac OSX package gets fixed. Thanks!

@t-oster

This comment has been minimized.

Show comment
Hide comment
@t-oster

t-oster Jul 26, 2013

Owner

Hi,

please check, if the file
/System/Library/Frameworks/JavaVM.framework/Resources/MacOS/JavaApplicationStub
exists on your system, and if so, try if replacing the
VisiCut.app/Contents/MacOS/JavaApplicationStub in the VisiCut.app-folder
(in finder, rightclick, show-contents) with the one from your system.
If it works, you could create a pull-request, or just send me the file,
since I have no Mac OS X at hand right now.

Owner

t-oster commented Jul 26, 2013

Hi,

please check, if the file
/System/Library/Frameworks/JavaVM.framework/Resources/MacOS/JavaApplicationStub
exists on your system, and if so, try if replacing the
VisiCut.app/Contents/MacOS/JavaApplicationStub in the VisiCut.app-folder
(in finder, rightclick, show-contents) with the one from your system.
If it works, you could create a pull-request, or just send me the file,
since I have no Mac OS X at hand right now.

@ewidance

This comment has been minimized.

Show comment
Hide comment
@ewidance

ewidance Aug 11, 2013

I've done it on my OSX 10.7. That works. How could i send you the /System/Library/Frameworks/JavaVM.framework/Resources/MacOS/JavaApplicationStub file?

ewidance commented Aug 11, 2013

I've done it on my OSX 10.7. That works. How could i send you the /System/Library/Frameworks/JavaVM.framework/Resources/MacOS/JavaApplicationStub file?

@t-oster

This comment has been minimized.

Show comment
Hide comment
@t-oster

t-oster Aug 11, 2013

Owner

If you are not familiar with git, just send it per mail. Otherwise the way would be forking visicut on github, push a commit to your fork an send me a pull request...which is overkill for one file anyway, but do as you like.
So it works with this stub on the latest java version?

Owner

t-oster commented Aug 11, 2013

If you are not familiar with git, just send it per mail. Otherwise the way would be forking visicut on github, push a commit to your fork an send me a pull request...which is overkill for one file anyway, but do as you like.
So it works with this stub on the latest java version?

@PhilipMcGaw

This comment has been minimized.

Show comment
Hide comment
@PhilipMcGaw

PhilipMcGaw Sep 7, 2013

Replacing the stub file worked for me. - update, and then it failed when I re-loaded VisiCut.

Current update:
Removed Java from system, and downloading the copy from http://support.apple.com/kb/DL1572

nope that doesn't work either.

PhilipMcGaw commented Sep 7, 2013

Replacing the stub file worked for me. - update, and then it failed when I re-loaded VisiCut.

Current update:
Removed Java from system, and downloading the copy from http://support.apple.com/kb/DL1572

nope that doesn't work either.

@t-oster

This comment has been minimized.

Show comment
Hide comment
@t-oster

t-oster Sep 8, 2013

Owner

Hmm... so maybe we have to move away from the Java Application Stub and write our own... We could either start java directly via bash-script (embedded in the .app package) or create a custom launcher similar to the application stub.

Owner

t-oster commented Sep 8, 2013

Hmm... so maybe we have to move away from the Java Application Stub and write our own... We could either start java directly via bash-script (embedded in the .app package) or create a custom launcher similar to the application stub.

@t-oster t-oster referenced this issue Jan 15, 2015

Merged

Release Version 1.8 #228

3 of 8 tasks complete

@t-oster t-oster added this to the VisiCut 1.8 milestone Jan 16, 2015

@mgmax

This comment has been minimized.

Show comment
Hide comment
@mgmax

mgmax May 17, 2015

Contributor

http://informagen.com/JarBundler/StubFile.html suggests symlinking the java stub.

Contributor

mgmax commented May 17, 2015

http://informagen.com/JarBundler/StubFile.html suggests symlinking the java stub.

@t-oster

This comment has been minimized.

Show comment
Hide comment
@t-oster

t-oster Jun 9, 2015

Owner

Looks like a solution. Who can test if this works? I would like the OSX build to work on most OSX versions possible.

Owner

t-oster commented Jun 9, 2015

Looks like a solution. Who can test if this works? I would like the OSX build to work on most OSX versions possible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment