Skip to content
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

Gooey installs fine on Windows, but doesn't start properly #414

Open
1 of 6 tasks
melanieganz opened this issue Dec 7, 2022 · 3 comments
Open
1 of 6 tasks

Gooey installs fine on Windows, but doesn't start properly #414

melanieganz opened this issue Dec 7, 2022 · 3 comments

Comments

@melanieganz
Copy link

Is it a new bug?

I did not find an existing issue about my problem

What is the problem?

For convenience I also wanted to try out the GUI on my Windows machine, and it installs fine and recognized my existing git and git-annex (both work fine in git bash). The Datalad Gooey shortcuts are there and when I click on it, a command windows appears for a second and then it closes again and nothing happens.

What steps will reproduce the problem?

Try to open the app via the shortcut on the desktop.

Additional context

No response

How did you install the App?

  • Via the Windows installer
  • Using pip (pip install datalad-gooey)
  • Using brew (brew install datalad-gooey)
  • Using conda (conda install -c forge datalad-gooey)
  • Not sure
  • Other

System information

Microsoft Windows 10 Enterprise

@welcome
Copy link

welcome bot commented Dec 7, 2022

Welcome Banner (Image: CC-BY license, The Turing Way Community, & Scriberia. Zenodo. http://doi.org/10.5281/zenodo.3332808) Hi there, and thank you for filing an issue. We're excited to have your input and welcome your idea! 😊

@mih
Copy link
Member

mih commented Dec 25, 2022

Hey, sorry for the delay. When you start it in the terminal, what does it say?

@jsheunis
Copy link
Member

jsheunis commented Sep 1, 2023

I've encountered this before with a windows user. They had first installed datalad on windows in the "standard way", and then also installed the gooey using the dedicated windows installer. The issue was resolved when they uninstalled everything and then only used the windows installer for the gooey. This of course does not identify or address the core problem.

And another data point: the same thing occurred yesterday at a workshop I presented.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants