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

Can't get past "settings" after clean install of 1.2.0-rc1 #130

Closed
jovandeginste opened this issue May 11, 2016 · 6 comments
Closed

Can't get past "settings" after clean install of 1.2.0-rc1 #130

jovandeginste opened this issue May 11, 2016 · 6 comments

Comments

@jovandeginste
Copy link

I installed the deb package on a clean machine, and got the settings popup. After filling in the team info, clicking 'save' did nothing.

I then downloaded 1.1.1 (tar.gz, no deb available). Settings worked as expected and generated a config.json in my ~/.config; again installed the deb and it went immediately to the team page. Now opening the settings dialog gives a black screen.

@yuya-oc
Copy link
Contributor

yuya-oc commented May 11, 2016

Could you tell me your environment? (See CONTRIBUTING.md)

@jovandeginste
Copy link
Author

jovandeginste commented May 11, 2016

DISTRIB_DESCRIPTION="Ubuntu 16.04 LTS"

Mattermost Team Edition:
Version:2.2.0
Build Number:6671
Build Date:Fri Apr 15 18:40:19 UTC 2016
Build Hash:8e883ad2f516820942cc0131241268c1ea909ff3

@jovandeginste
Copy link
Author

also, should have been blank screen instead of black

@yuya-oc yuya-oc added the Linux label May 11, 2016
@yuya-oc
Copy link
Contributor

yuya-oc commented May 11, 2016

~/.config/Mattermost is not created on clean environment, so 'save' did not work.

yuya-oc added a commit that referenced this issue May 12, 2016
Make sure the userData directory is created during the ready event of app
module.

Close #130
@yuya-oc
Copy link
Contributor

yuya-oc commented May 12, 2016

Could you try with this build? https://circleci.com/gh/mattermost/desktop/311#artifacts

@jovandeginste
Copy link
Author

This build seems to fix this issue. I tried it on a clean VM. I will close the issue, thanks!

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

No branches or pull requests

2 participants