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

Application initialization failed: no display name and no $DISPLAY environment variable #130

Closed
lpalli opened this Issue May 19, 2014 · 2 comments

Comments

Projects
None yet
3 participants
@lpalli

lpalli commented May 19, 2014

If it is possible how we must configure babun to use graphical tools like gitk ou git gui?
The installation work fine but the execution causes an error message:

Application initialization failed: no display name and no $DISPLAY environment variable
Error in startup script: invalid command name "tk_messageBox"
    while executing
"tk_messageBox  -icon error  -type ok  -title "git-gui: fatal error"  -message $err"
    invoked from within
"if {[catch {package require Tcl 8.4} err]
 || [catch {package require Tk  8.4} err]
} {
        catch {wm withdraw .}
        tk_messageBox \
                -icon error \
                -typ..."
    (file "/usr/lib/git-core/git-gui" line 34)
@tombujok

This comment has been minimized.

Contributor

tombujok commented May 20, 2014

It's a Cygwin issue - have a look here:
http://cygwin.com/ml/cygwin/2012-02/msg00318.html

@tombujok tombujok added the feedback label May 20, 2014

@tombujok tombujok closed this Feb 4, 2015

@oswaldo

This comment has been minimized.

oswaldo commented May 31, 2016

Actually that is not an issue.

You can use pact to install the required x packages. I believe I have done the following in my instance:

pact install xinit tcl-tk

Then launch the xserver with for instance:

startxwin

In another terminal, according to this documentation you should create the following environment variable:

export DISPLAY=:0.0

And then ssh with the -Y flag.

Works for me.

@tombujok, maybe you should try it yourself, possibly getting to more straight forward instructions and add that to the faq instead of a link to a issue which leads to the wrong conclusion of not being possible.

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